Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to ASM 6.2 [SPR-16398] #20944

Closed
spring-projects-issues opened this issue Jan 18, 2018 · 4 comments
Closed

Upgrade to ASM 6.2 [SPR-16398] #20944

spring-projects-issues opened this issue Jan 18, 2018 · 4 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jan 18, 2018

Juergen Hoeller opened SPR-16398 and commented

ASM 6.1 is tracking JDK 10, with its GA expected soon after JDK 10 GA.


Reference URL: https://gitlab.ow2.org/asm/asm/tree/master/asm/src/main/java/org/objectweb/asm

Issue Links:

Referenced from: commits 8a9d042, a1d2097

@spring-projects-issues
Copy link
Collaborator Author

Vladimir Tsanev commented

ASM 6.1 was released on 11 March

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Indeed, largely a refactoring without additional features... probably the widest-ranging refactoring in ASM's history though. In any case, we're going to pick it up for Spring Framework 5.1, also revisiting ASM's approach for accepting unknown class file versions. For the time being, our lenient ASM 6.0 fork in Spring Framework 5.0.x works against JDK 10 just as well.

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Since ASM 6.2 is out in the meantime, we'll upgrade to that version straight away, also bumping up CGLIB to 3.2.7 for Spring Framework 5.1 RC1.

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

I've upgraded our ASM fork to ASM master (effectively 6.2 GA + a few recent patches) which is likely the state that we'll release our 5.1 RC1 against in about two weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants