The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 12 Aug 2004 7:26 AM
Body:
When you get do a 'cvs co maven', you get the MAIN branch, which refers to the future
1.1 release.
To get the 1.0 branch (which will have a 1.0.1 tag/release at some point in the
future), you do a 'cvs co -r MAVEN-1_0-BRANCH maven' instead (prefereably in another
directory, as both commands will create a maven 'sub-directory').
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1424?page=comments#action_23038
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1424
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1424
Summary: maven -p with a non-existant pom file results in BUILD SUCCESSFUL
Type: Improvement
Status: Unassigned
Priority: Trivial
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
cli
Versions:
1.0
Assignee:
Reporter: Michael Mattox
Created: Wed, 11 Aug 2004 9:20 AM
Updated: Thu, 12 Aug 2004 7:26 AM
Environment: win2k, jdk1.4.2
Description:
maven -p with a non-existant pom file results in BUILD SUCCESSFUL. it should display
an error saying the pom file could not be found.
---------------------------------------------------------------------
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]