The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Fri, 23 Jul 2004 1:42 AM
Changes:
Fix Version changed to 1.0.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1383?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1383
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1383
Summary: If JAVA_HOME variable is not defined, it should throw an error level
Type: Bug
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
cli
Fix Fors:
1.0.1
Versions:
1.0
Assignee:
Reporter: Ben Walding
Created: Tue, 20 Jul 2004 7:31 PM
Updated: Fri, 23 Jul 2004 1:42 AM
Description:
At the moment, the error level is just the standard "success" error level of 0. This
means that a maven build failure can be missed by things like DamageControl.
Patch (yeah it should be attached, but it's 1 character on line 109). And I'll
probably apply it anyway.
--- maven.orig 2004-07-21 09:25:06.000000000 +1000
+++ maven 2004-07-21 09:27:00.000000000 +1000
@@ -109,7 +109,7 @@
if [ ! -x "$JAVACMD" ] ; then
echo "Error: JAVA_HOME is not defined correctly."
echo " We cannot execute $JAVACMD"
- exit
+ exit 1
fi
if [ -z "$JAVA_HOME" ] ; then
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
