maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (MNG-93) maven.reactor.excludes should always exclude pom.xml regardless of value
Date Sat, 16 Oct 2004 11:12:21 GMT
The following comment has been added to this issue:

     Author: Trygve Laugstol
    Created: Sat, 16 Oct 2004 7:11 AM
I don't think there is a issue with the root pom beeing included, I actually think it should
because maven will know that this is a "parent pom" and take the appropriate action (something
like pom:install).

The <type> handlers should perhaps include a default goal making parent poms included
in a reactor a non-issue.

Another argument is that they might need to be picked up if you want the reactor to be so
smart that it will install any parents before the children if they're missing from the local

View this comment:

View the issue:

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
   Fix Fors:

   Reporter: Brett Porter

    Created: Fri, 15 Oct 2004 10:35 PM
    Updated: Sat, 16 Oct 2004 7:11 AM

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?)

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message