You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Mike Perham <mp...@us.ibm.com> on 2006/08/22 17:50:28 UTC
build problem
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)
RE: build problem
Posted by Mike Perham <mp...@us.ibm.com>.
Patrick, yes, they are a way to compartmentalize variance between different
build environments. You guys are already using them in your top-level POM
which is why I thought it would be relatively familiar. Here's a decent
start although it does not seem to cover profile activation based on OS.
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
mike
"Patrick Linskey" <pl...@bea.com> wrote on 08/22/2006 01:04:56 PM:
> Are OS profiles a maven thing? Note that this list is populated largely
> with maven newbies.
>
> -Patrick
>
> --
> Patrick Linskey
> BEA Systems, Inc.
>
> > -----Original Message-----
> > From: Mike Perham [mailto:mperham@us.ibm.com]
> > Sent: Tuesday, August 22, 2006 11:01 AM
> > To: open-jpa-dev@incubator.apache.org
> > Subject: Re: build problem
> >
> >
> >
> >
> >
> >
> > 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" <mp...@gmail.com> 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)
> > >
> >
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
RE: build problem
Posted by Patrick Linskey <pl...@bea.com>.
Are OS profiles a maven thing? Note that this list is populated largely
with maven newbies.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
> -----Original Message-----
> From: Mike Perham [mailto:mperham@us.ibm.com]
> Sent: Tuesday, August 22, 2006 11:01 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: build problem
>
>
>
>
>
>
> 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" <mp...@gmail.com> 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)
> >
>
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: build problem
Posted by Mike Perham <mp...@us.ibm.com>.
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" <mp...@gmail.com> 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)
>
Re: build problem
Posted by Marc Prud'hommeaux <mp...@apache.org>.
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)