Marc, there's no reason but I'm just reporting a build failure due to my
environment. Someone else might have the same problem but not know what
the problem is or how to fix it. You should be able to use OS profiles to
extend my fix to work in OSX. I don't have an example of how to do this
handy unfortunately.
mike
"Marc Prud'hommeaux" <[EMAIL PROTECTED]> wrote on 08/22/2006
12:40:52 PM:
> Mike-
>
> > <jvm>${JAVA_HOME}/bin/java</jvm>
>
> Unfortunately, I don't think that's portable ... on OSX, the "java"
> command can be at ${JAVA_HOME}/Commands/java, and some versions of
> the IBM "java" command are at ${JAVA_HOME}/jre/sh/java.
>
> Is there some reason why you can't override both the JAVA_HOME and
> PATH when you want to change the version of Java you are using?
>
>
> On Aug 22, 2006, at 8:50 AM, Mike Perham wrote:
>
> >
> >
> >
> >
> >
> > OpenJPA fails to build when the JAVA_HOME is set to Java 5 but Java
> > 1.4 is
> > first in the path. This is because Maven 2 uses JAVA_HOME inside
> > "mvn" but
> > just executes "java" by default when forking the unit tests. The
> > fix is
> > relatively simple - override the surefire JVM setting:
> >
> > <build>
> > <pluginManagement>
> > <plugins>
> > <plugin>
> > <artifactId>maven-surefire-plugin</artifactId>
> > <configuration>
> > <jvm>${JAVA_HOME}/bin/java</jvm>
> > </configuration>
> > </plugin>
> > </plugins>
> > </pluginManagement>
> > </build>
> >
> > I believe this will be fixed in the next surefire release.
> > http://jira.codehaus.org/browse/MSUREFIRE-127
> >
> > mike
> > (Maven PMC member and hopeful OpenJPA user)
>
