-
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