The Aether project generally provides two sets of deliverables:
- Aether Core, i.e. the API, SPI, utility classes and base implementation of the library.
- Aether Ant Tasks, a collection of tasks for Apache Ant to employ Aether for interaction with repositories using the Apache Maven format.
In addition to providing binary and source distributions from the project's download area, Aether artifacts will be distributed via the Central Repository. Aether Core will also be made available as a P2 update site.
Compatibility with Sonatype Aether
API Contract Compatibility
To comply with Eclipse Foundation requirements, all Aether Java types/packages have been moved into the org.eclipse.aether namespace. No compatibility layer will be provided for users of Sonatype Aether.
To comply with Eclipse Foundation requirements, all Aether Java types/packages have been moved into the org.eclipse.aether namespace. While the API has undergone some refactoring and cleanup during the move to Eclipse, it is expected that typical clients mainly need to update their imports and make minor code changes to successfully build against the new Aether API.
None of the Aether deliverables are internationalized, any log and exception messages use English.
Aether consists of pure Java code and has no direct dependence on the underlying operating system. This release is expected to run on any JVM that supports Java SE 5 or newer.
Aether Ant Tasks target Apache Ant 1.7 or newer.
|M1||2012/10/05||First distribution of Aether Core from its new home at the Eclipse foundation to get things started.|
|M2||2013/02/20||Second milestone which among others features a redesigned conflict resolution logic and a P2 update site.|
|M3||2013/08/01||Third milestone to introduce a restructured transport layer SPI and first distribution of Aether Ant Tasks.|
|M4||2014/01/06||Forth milestone, rounding up repository connector SPI and allowing configuration of extension priorities.|