Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.3.1
-
None
-
Windows 8.1 Pro 64-bit
Description
I recently upgraded from Maven 3.0.4 to 3.3.1. It seems as if "mvn.cmd" no longer indicates failure properly when using "&&".
Invoking "mvn foo && echo SUCCESS!" using Maven 3.0.4 on Windows causes the following output (notice no trace of "SUCCESS!" as "mvn" fails):
c:\Temp>mvn foo && echo SUCCESS! [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.061s [INFO] Finished at: Tue Apr 28 14:08:27 CEST 2015 [INFO] Final Memory: 10M/491M [INFO] ------------------------------------------------------------------------ [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (c:\Temp). Please verify you invoked Maven from the correct directory. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
Invoking "mvn foo && echo SUCCESS!" using Maven 3.3.1 on Windows causes the following output (notice "SUCCESS!" is echoed even though "mvn" fails):
c:\Temp>mvn foo && echo SUCCESS! [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.053 s [INFO] Finished at: 2015-04-28T14:09:19+02:00 [INFO] Final Memory: 13M/491M [INFO] ------------------------------------------------------------------------ [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (c:\Temp). Please verify you invoked Maven from the correct directory. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException SUCCESS!
It is a little strange that it does not work in Maven 3.3.1 as invoking "mvn foo" actually causes "%ERRORLEVEL%" to be set to "1":
c:\Temp>mvn foo [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.052 s [INFO] Finished at: 2015-04-28T14:09:41+02:00 [INFO] Final Memory: 13M/491M [INFO] ------------------------------------------------------------------------ [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (c:\Temp). Please verify you invoked Maven from the correct directory. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException c:\Temp>echo %ERRORLEVEL% 1
Attachments
Issue Links
- is related to
-
MWRAPPER-27 rework mvnw* scripts to better match mvn* from Maven 3.8
-
- Closed
-
- relates to
-
MNG-5776 Drop support for Win9x in mvn launch scripts
-
- Closed
-
- mentioned in
-
Page Loading...