Are you sure what you need is feasible with javac? As Maven just uses it to compile, anything feasible with javac should be easy enough to pass through.
My 2 cents. Le 11 août 2011 19:27, "glenh" <[email protected]> a écrit : > Hey, > > We're using web service annotations for our application and running into a > strange problem. During compilation we get an error stating that it can't > find a specific constructor(s). The problem is that the class that has the > correct constructor is located in a third party jar (from geranimo and yes > I've specified in classpath/dependency) but the classloader is picking up a > similar class in the rt.jar (I'm assuming from the bootclasspath based on > how the classloader works I think). The particular class in question is the > Service class. > > I believe this has been corrected in jdk1.7 but unfortunately we need it for > jdk1.6. > > Is there a way I can ignore finding the class in rt.jar in maven? As a > temporary solution, we've specified the jar we want to use in the > bootclasspath when we invoke the compiler-plugin. I'm hoping we don't need > to write our own classloader if at all possible... > > Thanks in advance. > > -- > View this message in context: http://maven.40175.n5.nabble.com/problems-loading-correct-class-using-maven-2-2-1-and-jdk1-6-tp4690291p4690291.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
