Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: Continuum
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Brett Porter
            Reporter:
            Sebb
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development