You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2010/03/20 15:27:27 UTC
[jira] Created: (INFRA-2558) Add definitions of JAVA installations
Add definitions of JAVA installations
-------------------------------------
Key: INFRA-2558
URL: https://issues.apache.org/jira/browse/INFRA-2558
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Continuum
Reporter: Sebb
Commons has just updated its parent POM to allow the compilation and test phases of the build to use a different JVM from the one that is used to run Maven.
The different JVMs are enabled using profiles, however the profiles need to know the exact location of the various JVM installations.
This can be done either through environment variables, or better, by updating settings.xml.
For example, I have the following in my settings.xml:
<profile>
<id>java-1.3</id>
<properties>
<JAVA_1_3_HOME>C:\jdk1.3.1_20</JAVA_1_3_HOME>
</properties>
</profile>
<profile>
<id>java-1.4</id>
<properties>
<JAVA_1_4_HOME>C:\j2sdk1.4.2_19</JAVA_1_4_HOME>
</properties>
</profile>
<profile>
<id>java-1.5</id>
<properties>
<JAVA_1_5_HOME>C:\jdk1.5.0_22</JAVA_1_5_HOME>
</properties>
</profile>
<profile>
<id>java-1.6</id>
<properties>
<JAVA_1_6_HOME>C:\jdk1.6.0_18</JAVA_1_6_HOME>
</properties>
</profile>
These profiles are not enabled by default, so only affect builds that use them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2558) Add definitions of JAVA
installations
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894925#action_12894925 ]
Brett Porter commented on INFRA-2558:
-------------------------------------
sorry I missed this issue. I'll add these to vmbuild2 as it gets set up - we only have JDK 6 on there for now.
> Add definitions of JAVA installations
> -------------------------------------
>
> Key: INFRA-2558
> URL: https://issues.apache.org/jira/browse/INFRA-2558
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Continuum
> Reporter: Sebb
>
> Commons has just updated its parent POM to allow the compilation and test phases of the build to use a different JVM from the one that is used to run Maven.
> The different JVMs are enabled using profiles, however the profiles need to know the exact location of the various JVM installations.
> This can be done either through environment variables, or better, by updating settings.xml.
> For example, I have the following in my settings.xml:
> <profile>
> <id>java-1.3</id>
> <properties>
> <JAVA_1_3_HOME>C:\jdk1.3.1_20</JAVA_1_3_HOME>
> </properties>
> </profile>
> <profile>
> <id>java-1.4</id>
> <properties>
> <JAVA_1_4_HOME>C:\j2sdk1.4.2_19</JAVA_1_4_HOME>
> </properties>
> </profile>
> <profile>
> <id>java-1.5</id>
> <properties>
> <JAVA_1_5_HOME>C:\jdk1.5.0_22</JAVA_1_5_HOME>
> </properties>
> </profile>
> <profile>
> <id>java-1.6</id>
> <properties>
> <JAVA_1_6_HOME>C:\jdk1.6.0_18</JAVA_1_6_HOME>
> </properties>
> </profile>
> These profiles are not enabled by default, so only affect builds that use them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2558) Add definitions of JAVA installations
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed INFRA-2558.
-------------------------------
Assignee: Brett Porter
Resolution: Fixed
added for JDK 5 and JDK 6. The installers for J2SDK 1.4 and J2SDK 1.3 don't appear to work on amd64 linux.
> Add definitions of JAVA installations
> -------------------------------------
>
> Key: INFRA-2558
> URL: https://issues.apache.org/jira/browse/INFRA-2558
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Continuum
> Reporter: Sebb
> Assignee: Brett Porter
>
> Commons has just updated its parent POM to allow the compilation and test phases of the build to use a different JVM from the one that is used to run Maven.
> The different JVMs are enabled using profiles, however the profiles need to know the exact location of the various JVM installations.
> This can be done either through environment variables, or better, by updating settings.xml.
> For example, I have the following in my settings.xml:
> <profile>
> <id>java-1.3</id>
> <properties>
> <JAVA_1_3_HOME>C:\jdk1.3.1_20</JAVA_1_3_HOME>
> </properties>
> </profile>
> <profile>
> <id>java-1.4</id>
> <properties>
> <JAVA_1_4_HOME>C:\j2sdk1.4.2_19</JAVA_1_4_HOME>
> </properties>
> </profile>
> <profile>
> <id>java-1.5</id>
> <properties>
> <JAVA_1_5_HOME>C:\jdk1.5.0_22</JAVA_1_5_HOME>
> </properties>
> </profile>
> <profile>
> <id>java-1.6</id>
> <properties>
> <JAVA_1_6_HOME>C:\jdk1.6.0_18</JAVA_1_6_HOME>
> </properties>
> </profile>
> These profiles are not enabled by default, so only affect builds that use them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.