You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/01/27 08:01:26 UTC
[jira] Updated: (MNG-95) reactor failed project behaviour
The following issue has been updated:
Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
Date: Thu, 27 Jan 2005 2:00 AM
Changes:
Fix Version changed from 1.0-alpha-2
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-95?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-95
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-95
Summary: reactor failed project behaviour
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Assignee:
Reporter: Brett Porter
Created: Fri, 15 Oct 2004 10:43 PM
Updated: Thu, 27 Jan 2005 2:00 AM
Description:
reactor should have "ignoreFailures" like m1, but smarted.
failure setting:
- fail build on first subproject failure
- process all, but overall fail if there were any failures
- process all, report success regardless (eg, we were running site and want to continue with something else next)
Additionally, if the second two options are in play, a project should fail if one of its dependencies failed (eg if maven-artifact fails to build, so does maven-core, but maven-model does not)
---------------------------------------------------------------------
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