Le mardi 03 août 2010, Benjamin Bentmann a écrit : > Jason van Zyl wrote: > > At any rate we would like to merge these changes in and make plans to > > release 3.0-beta-2. > > Just in case, those changes currently live at > http://github.com/bentmann/maven-3/
I had a look at the branch, and don't understand how the new maven-artifact- descriptor module is used to extend Aether in Maven 3. The question of relations between Aether And Maven specifics is not clear to me for the moment: I'm digging deeper into the code. I have 3 questions: - aether-api: shouldn't it have its own release cycle, different from other modules? I worked on retro-documenting how reporting-api and doxia-api evolved over time, which releases where exactly the same code, and which ones added a little evolution, I think that having the same version for aether API and implementation will lead to same issues - RepositorySystem interface: resolveDependencies methods are about transitive dependencies, while other methods are about reading artifacts from or putting artifacts into repository. Transitive dependencies need to interpret pom content, while getting or putting an artifact doesn't require to understand pom format. Is it possible to have transitive dependency methods and classes into a different package? I think this is the part that can be extended, with lots of different options for algorithms, formats, and so on. - Aether seems really an interesting piece of software. But I still don't see how Maven and P2 will integrate their specific parts into Aether's umbrella. Is there something available about P2 integration? Regards, Hervé > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
