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

maven builder fails if latest maven on path on windows

    XMLWordPrintable

Details

    Description

      add the path to maven 3.3.9 to your PATH environment
      start Jenkins
      create a new freestyle job on windows
      add a maven step (-version)
      build the job

      expected results

      the output of maven is shown

      actual results

      build fails. Jenkins tries to invoke mvn.bat which does not exist.

      workaround

      add a maven installation and configure jobs to use that (untested)

      Causes several ATH failures on windows.

      Attachments

        Issue Links

          links to

          Web Link PR #2148

          Activity

            Ascending order - Click to sort in descending order
            teilo James Nord added a comment -

            not strictly available for LTS canditate nomination - however its abscence breaks some ATH tests on Windows, so please

            teilo James Nord added a comment - not strictly available for LTS canditate nomination - however its abscence breaks some ATH tests on Windows, so please
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: James Nord
            Path:
            core/src/main/java/hudson/tasks/Maven.java
            http://jenkins-ci.org/commit/jenkins/490adc9d0f4b0ed2c7e3183b18b136c006953824
            Log:
            [FIXED JENKINS-33693] Do not hardcode .bat extension.

            As the default maven command is on the path we can not hard code the
            command to mvn.bat as since maven 3.something it has been mvn.cmd

            As this is on the path we can just use mvn and let Windows do its thing
            with PATHEXT which will has both .BAT and .CMD by default.

            This fixes ATH failures when the ATH is run on windows.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: James Nord Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/490adc9d0f4b0ed2c7e3183b18b136c006953824 Log: [FIXED JENKINS-33693] Do not hardcode .bat extension. As the default maven command is on the path we can not hard code the command to mvn.bat as since maven 3.something it has been mvn.cmd As this is on the path we can just use mvn and let Windows do its thing with PATHEXT which will has both .BAT and .CMD by default. This fixes ATH failures when the ATH is run on windows.
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: James Nord
            Path:
            core/src/main/java/hudson/tasks/Maven.java
            http://jenkins-ci.org/commit/jenkins/573d0920dbaa4b2b48d839b865141a097c3b87fd
            Log:
            Merge pull request #2148 from jtnord/jenkins-33693

            [FIXED JENKINS-33693] Do not hardcode .bat extension.

            Compare: https://github.com/jenkinsci/jenkins/compare/5999996aa36e...573d0920dbaa

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: James Nord Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/573d0920dbaa4b2b48d839b865141a097c3b87fd Log: Merge pull request #2148 from jtnord/jenkins-33693 [FIXED JENKINS-33693] Do not hardcode .bat extension. Compare: https://github.com/jenkinsci/jenkins/compare/5999996aa36e...573d0920dbaa
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #4523
            [FIXED JENKINS-33693] Do not hardcode .bat extension. (Revision 490adc9d0f4b0ed2c7e3183b18b136c006953824)

            Result = SUCCESS
            james nord : 490adc9d0f4b0ed2c7e3183b18b136c006953824
            Files :

            • core/src/main/java/hudson/tasks/Maven.java
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #4523 [FIXED JENKINS-33693] Do not hardcode .bat extension. (Revision 490adc9d0f4b0ed2c7e3183b18b136c006953824) Result = SUCCESS james nord : 490adc9d0f4b0ed2c7e3183b18b136c006953824 Files : core/src/main/java/hudson/tasks/Maven.java
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: James Nord
            Path:
            core/src/main/java/hudson/tasks/Maven.java
            http://jenkins-ci.org/commit/jenkins/89532690e6e334993c44814b82fae916c4ffae99
            Log:
            [FIXED JENKINS-33693] Do not hardcode .bat extension.

            As the default maven command is on the path we can not hard code the
            command to mvn.bat as since maven 3.something it has been mvn.cmd

            As this is on the path we can just use mvn and let Windows do its thing
            with PATHEXT which will has both .BAT and .CMD by default.

            This fixes ATH failures when the ATH is run on windows.

            (cherry picked from commit 490adc9d0f4b0ed2c7e3183b18b136c006953824)

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: James Nord Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/89532690e6e334993c44814b82fae916c4ffae99 Log: [FIXED JENKINS-33693] Do not hardcode .bat extension. As the default maven command is on the path we can not hard code the command to mvn.bat as since maven 3.something it has been mvn.cmd As this is on the path we can just use mvn and let Windows do its thing with PATHEXT which will has both .BAT and .CMD by default. This fixes ATH failures when the ATH is run on windows. (cherry picked from commit 490adc9d0f4b0ed2c7e3183b18b136c006953824)

            People

              Unassigned Unassigned
              teilo James Nord
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: