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 21:16:59 UTC
[jira] Updated: (MNG-93) maven.reactor.excludes should always exclude pom.xml regardless of value
The following issue has been updated:
Updater: Jason van Zyl (mailto:jvanzyl@maven.org)
Date: Thu, 27 Jan 2005 3:16 PM
Changes:
Fix Version changed from 1.0-alpha-1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-93?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-93
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-93
Summary: maven.reactor.excludes should always exclude pom.xml regardless of value
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Assignee:
Reporter: Brett Porter
Created: Fri, 15 Oct 2004 10:35 PM
Updated: Thu, 27 Jan 2005 3:16 PM
Description:
currently the maven.reactor.excludes property default to pom.xml.
However, setting it to something else means ${basedir}/pom.xml gets included, which never makes sense (that I can think of).
Set the default to "" and then always prepend ${basedir}/pom.xml. A new property would be needed if forcing the current pom to be included ever made sense (maybe on site?)
---------------------------------------------------------------------
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