[
https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-24380:
-------------------------------
Description:
In order to be able to more easily run server and webservices projects' tests, I
suggest we set default values in parent pom:
{code}
- <jbosstools.test.jre.5></jbosstools.test.jre.5>
- <jbosstools.test.jre.6></jbosstools.test.jre.6>
- <jbosstools.test.jre.7></jbosstools.test.jre.7>
- <jbosstools.test.jre.8></jbosstools.test.jre.8>
+ <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
+ <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
+ <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
+ <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
{code}
This way, depending on what your system's definition of JAVA_HOME happens to be, you
get a different effective pom, for your required JDK:
{code}
$ export JAVA_HOME=/opt/jdk1.8.0/
$ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
<jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5>
<jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6>
<jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7>
<jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8>
(or, to use the JAVA_HOME set by alternatives...)
$ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e
"s#.\+ \(.\+\)bin/java#\1#")
$ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
<jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5>
<jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6>
<jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7>
<jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8>
{code}
was:
In order to be able to more easily run server and webservices projects' tests, I
suggest we set default values in parent pom:
{code}
- <jbosstools.test.jre.5></jbosstools.test.jre.5>
- <jbosstools.test.jre.6></jbosstools.test.jre.6>
- <jbosstools.test.jre.7></jbosstools.test.jre.7>
- <jbosstools.test.jre.8></jbosstools.test.jre.8>
+ <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
+ <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
+ <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
+ <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
{code}
new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}
-------------------------------------------------------------------
Key: JBIDE-24380
URL:
https://issues.jboss.org/browse/JBIDE-24380
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
Fix For: 4.5.0.AM1
In order to be able to more easily run server and webservices projects' tests, I
suggest we set default values in parent pom:
{code}
- <jbosstools.test.jre.5></jbosstools.test.jre.5>
- <jbosstools.test.jre.6></jbosstools.test.jre.6>
- <jbosstools.test.jre.7></jbosstools.test.jre.7>
- <jbosstools.test.jre.8></jbosstools.test.jre.8>
+ <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5>
+ <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6>
+ <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7>
+ <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8>
{code}
This way, depending on what your system's definition of JAVA_HOME happens to be, you
get a different effective pom, for your required JDK:
{code}
$ export JAVA_HOME=/opt/jdk1.8.0/
$ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
<jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5>
<jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6>
<jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7>
<jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8>
(or, to use the JAVA_HOME set by alternatives...)
$ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e
"s#.\+ \(.\+\)bin/java#\1#")
$ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre
<jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5>
<jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6>
<jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7>
<jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)