A bit more detail from sh -x on the mvn command ... 1.5 goes in, 1.6 comes out.
+ '[' -z '' ']'
+ '[' -n /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home ']'
+ '[' -x
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/jre/sh/java
']'
+
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:
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
: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Wednesday, November 04, 2009 1:37 PM
To: Maven Users List
Subject: Re: Can't seem to get rid of 1.6
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
List
Subject: Re: Can't seem to get rid of 1.6
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
