-
Notifications
You must be signed in to change notification settings - Fork 38.6k
Closed
Labels
in: coreIssues in core modules (aop, beans, core, context, expression)Issues in core modules (aop, beans, core, context, expression)type: taskA general taskA general task
Milestone
Description
Juergen Hoeller opened SPR-14514 and commented
For Spring Framework 5.0 milestones, we keep using our variant of ASM 5.1, leniently accepting the 1.9 bytecode level but not having actual support for it. Once ASM 6.0 matures beyond its current alpha, we should upgrade our fork to it.
Affects: 5.0 M1
Reference URL: http://websvn.ow2.org/listing.php?repname=asm&path=%2Fbranches%2FASM_6_FUTURE%2Fasm%2Fsrc%2Forg%2Fobjectweb%2Fasm%2F
Issue Links:
- Upgrade to ASM 5.1 [SPR-14037] #18609 Upgrade to ASM 5.1
- Upgrade to ASM 5.2 [SPR-15071] #19637 Upgrade to ASM 5.2
- Upgrade to Gradle 4.1 for clean JDK 9 build compatibility [SPR-15667] #20226 Upgrade to Gradle 4.1 for clean JDK 9 build compatibility
- Compatibility with JDK 9 GA [SPR-15992] #18941 Compatibility with JDK 9 GA
- Upgrade to ASM 6.2 [SPR-16398] #20944 Upgrade to ASM 6.2
- Upgrade to ASM 6.0 level (for CGLIB 3.2.6) [SPR-16405] #20951 Upgrade to ASM 6.0 level (for CGLIB 3.2.6)
- Upgrade to ASM 7.0 [SPR-17267] #21800 Upgrade to ASM 7.0
Referenced from: commits 8a2262e, 185c2bf
1 votes, 2 watchers
Metadata
Metadata
Assignees
Labels
in: coreIssues in core modules (aop, beans, core, context, expression)Issues in core modules (aop, beans, core, context, expression)type: taskA general taskA general task