-
Bug
-
Resolution: Fixed
-
Major
-
Windows
When using Maven 3.3 on a Windows Jenkins instance, builds fail on post-build tasks that depend on Maven, for example the Sonar plugin. In the console output you would see: "Couldn’t find any executable in [maven path]".
The reason for this is that Maven 3.3 now ships '.cmd' files instead of '.bat' files, and Jenkins checks specifically for the presence of '.bat'.
- is duplicated by
-
JENKINS-27525 Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine
-
- Resolved
-
-
JENKINS-27705 Maven pre-build step is broken with Maven 3.3.1
-
- Resolved
-
[JENKINS-28232] Maven post-build task breaks when using Maven 3.3 on Windows
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | Original: Martijn Baay [ martijnb ] | New: Olivier Lamy [ olamy ] |
Labels | New: lts-candidate |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Labels | Original: lts-candidate | New: 1.609.2-fixed |
Workflow | Original: JNJira [ 163061 ] | New: JNJira + In-Review [ 197092 ] |