That doesn't help with bootclasspath inventory. However, I've found my problem. On MacOS snow leopard, the So-called Java 1.5 home is actually java 1.6!
On Wed, Nov 4, 2009 at 1:29 PM, Damon Jacobsen <dajacob...@lifetouch.com> wrote: > My understanding is the by using that target attribute, maven is still using > the default java installation to compile, but the byte code generated will be > compatible with the java version specified. > > Damon > > -----Original Message----- > From: Benson Margulies [mailto:bimargul...@gmail.com] > Sent: Wednesday, November 04, 2009 10:24 AM > To: Maven Users List > Subject: Can't seem to get rid of 1.6 > > I have set JAVA_HOME to a 1.5 java home. > > I have traced the mvn shell script to watch it get used. > > I have set <source/> and <target/> in the compiler plugin to 1.5. I > have checked the results with help:effective-pom. > > Nonetheless, code that calls the new > DocumentBuilderFactory.newInstance(<several args>) compiles and even > runs with no errors. > > I can't easily deinstall 1.6 from my mac. Has anyone else got a > suggestion what stupid mistake I'm making here? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > _____________________________________________________________________ > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
