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

Spring 4.0.0.RELEASE depends on aspectjweaver 1.8.0.M1 not found in Maven Central [SPR-11273] #15898

Closed
spring-issuemaster opened this issue Jan 1, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Jan 1, 2014

Janne Sinivirta opened SPR-11273 and commented

Spring 4.0.0.RELEASE depends on aspectjweaver 1.8.0.M1 which is not found in Maven Central.


Affects: 4.0 GA

Issue Links:

  • #20525 Upgrade to AspectJ 1.9 beta 7
  • #15873 Revisit spring-aspects 4.0.0 dependency on AspectJ 1.8.0.M1

1 votes, 5 watchers

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Jan 2, 2014

Juergen Hoeller commented

See the discussion at #15873: As noted there, Spring Framework 4.0 supports AspectJ 1.7 as well as 1.8 M1. We need the latter for building the framework on JDK 8 - however, at runtime, the choice is up to you.

That said, we have a few explicit dependencies on AspectJ that we're exporting in our POMs. Maybe we need to reconsider what we do for the time being, until AspectJ 1.8 is final (which it won't be before Q2 2014).

Juergen

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Jan 20, 2014

Juergen Hoeller commented

We're xposing AspectJ 1.7.4 to the public now, only using AspectJ 1.8.0.M1 for ajc in our build. This should be a fine compromise for the time being, since AspectJ 1.7.4 works fine with JDK 8 as well - for all the purposes that users need our declared dependencies for (i.e. pointcut evaluation and load-time weaving). If somebody wants to use ajc in their own build, they'll have to declare a specific AspectJ version for that task in their custom build anyway.

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.