-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins Node running on Windows
The new apache maven version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error:
FATAL: Couldn’t find any executable in D:\current-maven
I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only.
It can be fixed by creating a link with mklink on windows like
current-maven/bin> mklink mvn.bat mvn.cmd
- is related to
-
JENKINS-28629 Fix Apache Maven 3.3 support
-
- Resolved
-
[JENKINS-28373] apache maven 3.3.3 cannot be invoked anymore on windows
Description |
Original:
The new apache version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error: {{FATAL: Couldn’t find any executable in D:\current-maven}} I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only. It can be fixed my creating a link with mklink on windows like {{current-maven/bin> mklink mvn.bat mvn.cmd }} |
New:
The new apache version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error: {{FATAL: Couldn’t find any executable in D:\current-maven}} I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only. It can be fixed my creating a link with mklink on windows like {{current-maven/bin> mklink mvn.bat mvn.cmd}} |
Description |
Original:
The new apache version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error: {{FATAL: Couldn’t find any executable in D:\current-maven}} I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only. It can be fixed my creating a link with mklink on windows like {{current-maven/bin> mklink mvn.bat mvn.cmd}} |
New:
The new apache version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error: {{FATAL: Couldn’t find any executable in D:\current-maven}} I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only. It can be fixed by creating a link with {{mklink}} on windows like {{current-maven/bin> mklink mvn.bat mvn.cmd}} |
Description |
Original:
The new apache version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error: {{FATAL: Couldn’t find any executable in D:\current-maven}} I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only. It can be fixed by creating a link with {{mklink}} on windows like {{current-maven/bin> mklink mvn.bat mvn.cmd}} |
New:
The new apache maven version 3.3.3 has removed the "mvn.bat" file and introduced a new file "mvn.cmd". If we use this version in our maven style builds, we get more or less the following error: {{FATAL: Couldn’t find any executable in D:\current-maven}} I looks like, the Jenkins maven build always calls "mvn.bat" instead of "mvn" only. It can be fixed by creating a link with {{mklink}} on windows like {{current-maven/bin> mklink mvn.bat mvn.cmd}} |
Link |
New:
This issue is related to |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: maven-invoker-plugin [ 16822 ] |
Workflow | Original: JNJira [ 163211 ] | New: JNJira + In-Review [ 181136 ] |
Assignee | Original: Olivier Lamy [ olamy ] |
I have seen that this issue is fixed in a recent jenkins version? (we have switched to LTS .. so not checked if it was closed already here).