The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 12 Aug 2004 7:48 AM
Body:
I don't that's a way to ensure that. What you can do, though, is apply some changes in
a branch (1.0, in this case) and then merge them back to the main trunk - I haven't
done that because this patch is just a small change, so I don't think it worths the
overhead.
PS: before you ask, I don't remember the CVS commands to do this kind of merge
(haven't used this feature for a while), but it might be described at the CVS book
(that online version).
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1424?page=comments#action_23044
---------------------------------------------------------------------
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:48 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]
