The following comment has been added to this issue:
Author: Ronald Blaschke
Created: Sun, 18 Apr 2004 11:45 AM
Body:
A batch file is executed via a cmd.exe command shell, either the
current one or a new one. When Ant's
is used, a new shell is spawned which executes the batch fil
The following comment has been added to this issue:
Author: Brian Conlon
Created: Fri, 9 Apr 2004 2:06 PM
Body:
I have to agree with Bryan on this one. I have exactly the same requirement to call
Maven from Ant and have likewise been unsuccessful with the MavenTask. Because of I
The following comment has been added to this issue:
Author: Bryan Davis
Created: Sun, 4 Apr 2004 4:11 PM
Body:
Hm. I don't really understand why this is not a Maven issue. My company's build
machine only invokes Ant, so I have a build.xml which does an Ant to run the
Maven com
The following comment has been added to this issue:
Author: Ronald Blaschke
Created: Thu, 5 Feb 2004 9:00 AM
Body:
I have played around with this a bit on WinXP, and it seems like "exit /b %exit_code%"
just sets the ERRORLEVEL and finishes the current batch script, whereas "exit
The following comment has been added to this issue:
Author: Tim Anderson
Created: Wed, 4 Feb 2004 8:12 PM
Body:
It may need to be:
exit /B %ERRORLEVEL%
to avoid terminating cmd.exe if maven.bat was invoked from
the command line.
--
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 4 Feb 2004 7:58 PM
Body:
Seems harmless to add this in
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.js
The following comment has been added to this issue:
Author: Ronald Blaschke
Created: Thu, 22 Jan 2004 2:11 PM
Body:
Please drop this request, this is not a maven issue.
Windows batch files are quite different from processes, and are always executed in the
context of a command pro
The following comment has been added to this issue:
Author: Ronald Blaschke
Created: Thu, 22 Jan 2004 6:02 AM
Body:
This can be fixed, at least for Windows XP, by adding the following statement in the
last line of maven.bat.
exit %ERRORLEVEL%
Thereby resolving the original issue