You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Petr Bodnar (JIRA)" <ji...@apache.org> on 2016/05/10 15:49:12 UTC
[jira] [Comment Edited] (MNG-5815) "mvn.cmd" does not indicate
failure properly when using "&&"
[ https://issues.apache.org/jira/browse/MNG-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278268#comment-15278268 ]
Petr Bodnar edited comment on MNG-5815 at 5/10/16 3:48 PM:
-----------------------------------------------------------
OK, so the solution to make this work seems to be easy (tested on Windows XP & Windows 7): Simply replace the last line of {{exit /B %ERROR_CODE%}} with {{cmd /C exit /B %ERROR_CODE%}} inside the _mvn.cmd_. The question now is why the {{cmd /C}} was removed, most probably while implementing MNG-5776 ([~agudian]?).
Additionally, we can remove the redundant line {{@setlocal}} in order to get the proper {{%ERROR_CODE%}} (solution taken from MNG-5963).
was (Author: pbodnar):
OK, so the solutions to make this work seems to be easy (tested on Windows XP & Windows 7): Simply replace the last line of {{exit /B %ERROR_CODE%}} with {{cmd /C exit /B %ERROR_CODE%}} inside the _mvn.cmd_. The question now is why the {{cmd /C}} was removed, most probably while implementing MNG-5776 ([~agudian]?).
Additionally, we can remove the redundant line {{@setlocal}} in order to get the proper {{%ERROR_CODE%}} (solution taken from MNG-5963).
> "mvn.cmd" does not indicate failure properly when using "&&"
> ------------------------------------------------------------
>
> Key: MNG-5815
> URL: https://issues.apache.org/jira/browse/MNG-5815
> Project: Maven
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.3.1
> Environment: Windows 8.1 Pro 64-bit
> Reporter: Peter Kjær Guldbæk
>
> 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):
> {noformat}
> 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
> {noformat}
> Invoking "mvn foo && echo SUCCESS!" using Maven 3.3.1 on Windows causes the following output (notice "SUCCESS!" is echoed even though "mvn" fails):
> {noformat}
> 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!
> {noformat}
> 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":
> {noformat}
> 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
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)