Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Aether has been at Eclipse for several years, but the project has never garnered much of a community and the only real consumer of note is the Apache Maven project. The number of contributions have been slight and the people who have wanted to make larger contributions are confused by the project being at Eclipse. We also recently lost the person who did the majority of the work on the project. Given the requirement of Apache Maven on Aether the development team feels it's best for the project to go back to Apache where the Apache Maven committers are more apt to contirbute to the code, and hopefully community members as well.
- Log in to post comments
Aether has been at Eclipse
Submitted by Jason van Zyl on Wed, 02/03/2016 - 17:06
Aether has been at Eclipse for several years, but the project has never garnered much of a community and the only real consumer of note is the Apache Maven project. The number of contributions have been slight and the people who have wanted to make larger contributions are confused by the project being at Eclipse. We also recently lost the person who did the majority of the work on the project. Given the requirement of Apache Maven on Aether I feel it's best for the project to go back to Apache where the Apache Maven committers are more apt to contirbute to the code, and hopefully community members as well.
Two things that we are asking
Submitted by Jason van Zyl on Sat, 02/06/2016 - 08:22
Two things that we are asking upon termination is that we be able to change the license from EPL 1.0 to ASL 2.0 and retain the org.eclipse.aether package names for as long as necessary.
I have contact all contributors and committers and received their permission to change the license and I have recorded that here:
https://github.com/jvanzyl/aether-core/blob/master/aether-to-apache.txt
As for the package names we have put our users through a lot of pain and I would ask to keep them the same. We plan to refactor the interface between Maven and Aether so ultimately Aether will be an internal implementation detail but currently it is not. We will break users changing the package names and we would prefer not to do that.
Thanks to Eclipse foundation
Submitted by Herve Boutemy on Sat, 02/25/2017 - 03:19
Thanks to Eclipse foundation kind help, we were able to migrate Eclipse Aether to Apache Maven Artifact Resolver keeping binary compatible code: really thank you
The new Apache Maven Artifact Resolver component is available at https://maven.apache.org/resolver/
It will be used by Apache Maven 3.5 (which is transparent, since it is binary compatible)