Closed
Description
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:
- Pointcut evaluation fails against AbstractHandlerMethodMapping$MappingRegistry with AspectJ 1.8.10 [SPR-15019] #19586 Pointcut evaluation fails against AbstractHandlerMethodMapping$MappingRegistry with AspectJ 1.8.10
- spring-aspects should remain on AspectJ 1.8.9 by default (since aspectjrt 1.8.10 requires Java 7+) [SPR-15836] #20391 spring-aspects should remain on AspectJ 1.8.9 by default (since aspectjrt 1.8.10 requires Java 7+)
- Compatibility with JDK 9 GA [SPR-15992] #18941 Compatibility with JDK 9 GA
- Upgrade to AspectJ 1.9 beta 3 (for build compatibility with JDK 9 build 95+) [SPR-13839] #18412 Upgrade to AspectJ 1.9 beta 3 (for build compatibility with JDK 9 build 95+)
- Spring 4.0.0.RELEASE depends on aspectjweaver 1.8.0.M1 not found in Maven Central [SPR-11273] #15898 Spring 4.0.0.RELEASE depends on aspectjweaver 1.8.0.M1 not found in Maven Central
- Upgrade to AspectJ 1.9 RC1 [SPR-16077] #20626 Upgrade to AspectJ 1.9 RC1