You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently building against AspectJ 1.9 beta 6 for JDK 9 compatibility in our test suite. It'd be great to get out of beta there for our 5.0 GA release.
If AspectJ 1.9 remains in pre-release stage for some further time, we'll have to separate the version that we're exposing in the spring-aspects POM (downgraded to 1.8.10) from the one that we use in our framework build (latest 1.9 milestone), eventually catching up once AspectJ 1.9 goes GA.
AspectJ 1.9 beta 7 is available now, so we're going to use this one for ajc in spring-aspects (where we actually need a special JDK compatible version) and for running the spring-aop tests (since several tests otherwise won't pass)... while exposing AspectJ 1.8.10 as a runtime dependency in our Maven POMs (which is known to work on JDK 9 as well for common purposes, and can be individually upgraded to 1.9 in user POMs if necessary).
We're exposing AspectJ 1.8.11 now, also for the spring-aop and spring-context tests where it's known to work fine on JDK 9 for our purposes. So AspectJ 1.9 beta 7 is only used for ajc in spring-aspects now, as originally intended.
Juergen Hoeller opened SPR-15974 and commented
We're currently building against AspectJ 1.9 beta 6 for JDK 9 compatibility in our test suite. It'd be great to get out of beta there for our 5.0 GA release.
If AspectJ 1.9 remains in pre-release stage for some further time, we'll have to separate the version that we're exposing in the
spring-aspects
POM (downgraded to 1.8.10) from the one that we use in our framework build (latest 1.9 milestone), eventually catching up once AspectJ 1.9 goes GA.Affects: 5.0 RC4
Issue Links:
The text was updated successfully, but these errors were encountered: