Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3625

Tool Overrides are not taken in account by Maven2 projects

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      When using Maven2 in a distributed build setup, I cannot use the "tool override"
      feature. Here's an example:

      I set a tool overrride for, let's say, JDK1.6_generic, which is defined in the
      server as "C:\Java\JDK1.6_0_11" - and I override it with "E:\Java\JDK1.6_0_07".
      The Maven2 project will not take my override value into account, and will use
      the Server Default value.

          [JENKINS-3625] Tool Overrides are not taken in account by Maven2 projects

          Andrew Bayer added a comment -

          I'm not sure what you mean, exactly - do you mean that a node-specific tool location doesn't get picked up by the Maven project?

          Andrew Bayer added a comment - I'm not sure what you mean, exactly - do you mean that a node-specific tool location doesn't get picked up by the Maven project?

          Yes. Node specific tool locations are not taken into account. Example:

          On Linux master: MAVEN_221-ARTIMIRROR
          /home/axhudson/tools/maven/apache-maven-2.2.1-artimirror

          On Windows/Cygwin slave: MAVEN_221-ARTIMIRROR
          /cygdrive/c/tools/maven/maven-2.2.1

          Running env in a Maven 2 job (M2 extra build steps:
          MAVEN_221-ARTIMIRROR=/home/axhudson/tools/maven/apache-maven-2.2.1-artimirror

          And of course, Maven launch fails:
          ERROR: No classworlds*.jar found in \home\axhudson\tools\maven\apache-maven-2.1.0-artimirror – Is this a valid maven2 directory?

          I'm sad

          Costin Caraivan added a comment - Yes. Node specific tool locations are not taken into account. Example: On Linux master: MAVEN_221-ARTIMIRROR /home/axhudson/tools/maven/apache-maven-2.2.1-artimirror On Windows/Cygwin slave: MAVEN_221-ARTIMIRROR /cygdrive/c/tools/maven/maven-2.2.1 Running env in a Maven 2 job (M2 extra build steps: MAVEN_221-ARTIMIRROR=/home/axhudson/tools/maven/apache-maven-2.2.1-artimirror And of course, Maven launch fails: ERROR: No classworlds*.jar found in \home\axhudson\tools\maven\apache-maven-2.1.0-artimirror – Is this a valid maven2 directory? I'm sad

            Unassigned Unassigned
            cybik Renaud Lepage
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: