Hi Toni, very good idea. I need a quiet moment to read and understand your proposal in detail, though...
Some other points I noticed while working on Pax URL 1.4.0 snaphots: - Maven repository handling is growing into a maintenance nightmare. Wiki, Javadoc and implementations are diverging, test coverage is insufficient, and the desired behaviour is unclear. - Is it necessary to parse settings.xml? Aether must have an API for that... - Do we need to hard-code the central repository URL? Where does Maven get it from - the Super POM? Does Aether or some other Maven component offer a suitable API? Would be good to see that cleaned up in Pax URL 2.x. Cheers, Harald 2012/2/6 Toni Menzel <t...@okidokiteam.com>: > Gang, > > Last weekend I've start on a Pax URL Aether fork using Eclipse Aether + some > alternative ways to actually use Pax URL safely in non OSGi environments. > Reason for the latter improvement is that i found a nasty collision in Pax > Runner+Exam+URL which made me rethink alternatives to the global singleton > URL Handler approach (which i know is one of the major selling points of Pax > URL for sure, but it comes with drawbacks). > > For this, I've just opened a Wiki collecting ideas and directions for what > i'd call "Pax URL 2": http://team.ops4j.org/wiki/display/paxurl/PaxURL2Draft > > Toni > > -- > Toni Menzel Source > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
