[
http://jira.codehaus.org/browse/MNG-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150609#action_150609
]
Benjamin Bentmann commented on MNG-3271:
----------------------------------------
This is broken as of Maven 2.0.3, probably due to the change for MNG-1999. The
excludeDefaults flag does not properly survive the inheritance, core IT has
been created to reproduce this.
> <excludeDefaults> does not seem to work
> ---------------------------------------
>
> Key: MNG-3271
> URL: http://jira.codehaus.org/browse/MNG-3271
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.0.7
> Reporter: Grégory Joseph
> Fix For: 2.0.x
>
>
> As far as I understand, adding
> <excludeDefaults>true</excludeDefaults>
> in the <reporting> section of my pom should have the same effect as
> {code}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-project-info-reports-plugin</artifactId>
> <reportSets>
> <reportSet></reportSet>
> </reportSets>
> </plugin>
> {code}
> ... but only that latter had any effect.
> (I was mainly trying to disable the dependencies report, because I have many
> dependencies build with m1 which don't have a proper m2 pom)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
