I did not read through the whole thread, so maybe I missed (sorry for that).
Afaik maven plugins use a different ClassLoader hierarchy than you might expect. Most frameworks use ParentClassLoaderFirst, but maven afaik uses ClientClassLoaderFirst. Which means it's perfectly fine to to put a javax.* dependency in your plugin classpath. The only thing which is not allowed is to overwrite native SE stuff. LieGrue, strub ----- Original Message ----- > From: Benson Margulies <bimargul...@gmail.com> > To: Maven Users List <users@maven.apache.org> > Cc: > Sent: Tuesday, September 25, 2012 8:08 PM > Subject: Re: How to put a dependency in the classpath BEFORE jre.jar? > > Markus, > > If you want to join in on the fun of the development community, please > join us on the dev list. As you've heard on this thread, your > particular concern smacks into a messy conundrum about our desire to > avoid breaking other people's tools that read poms -- no matter how > poorly coded. However, there is a design in progress, it needs more > refinement, and mostly it will need people to actually code it. > > --benson > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
