• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Jenkins 1.606, Windows 7

      The "Invoke top-level Maven targets" pre-build step is broken when using Maven 3.3.1. The cause appears to be in hudson.tasks.Maven$DecideDefaultMavenCommand, which automatically appends ".bat" if running on Windows. In Maven 3.3.1, mvn.bat was renamed to mvn.cmd.

      Obviously this could be fixed but it might be a better idea to move this functionality to the Maven Plugin, which has more sophisticated Maven handling and works fine with 3.3.1.

          [JENKINS-27705] Maven pre-build step is broken with Maven 3.3.1

          Rich DiCroce created issue -
          Stephan Pauxberger made changes -
          Link New: This issue is duplicated by JENKINS-27525 [ JENKINS-27525 ]
          Daniel Beck made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Link New: This issue duplicates JENKINS-28232 [ JENKINS-28232 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 162018 ] New: JNJira + In-Review [ 196913 ]

            Unassigned Unassigned
            rcd Rich DiCroce
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: