Just a short notice, i merged the aether feature branch into master, so it gets included into the next 1.7 release. I am testing it now and also will very likely pull over the runner-repository (the ones for profiles) to github, too.
How it is included in Pax Runner: - added the artifact pax-url-aether - registered the "aether:" protocol in properties. The rest is protocol delegation from mvn->aether in Pax URL. So the code change for pax runner is quite small. This change brings: PRO: - native artifact resolution (instead of "maven like resolution"). Remember: Aether is not Maven. Aether is the good parts of Maven. - much better offline support via local caching in m2 repo just like maven itself does by default. CON: - pax runner assembly gains weight due to aether and its deps being included - profiles do use version-less coordinates (usually). This translates to an open ranged version declaration, which .. is basically a brute force crawling on your repo. The project Pax-Repository will change this (by not using a url for this at all) You can argue here if its worth the trade-offs, but its clear that, if Pax Runner has complains, its the "just maven like but not really" artifact resolution and mechanics. -- *Toni Menzel - http://www.okidokiteam.com*
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
