Maven 2 & 3

<excludeDefaults> does not seem to work

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.7
  • Fix Version/s: 2.0.10, 2.1.0
  • Component/s: POM
  • Labels:
    None
  • Number of attachments :
    0

Description

As far as I understand, adding
<excludeDefaults>true</excludeDefaults>
in the <reporting> section of my pom should have the same effect as

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-project-info-reports-plugin</artifactId>
                <reportSets>
                    <reportSet></reportSet>
                </reportSets>
            </plugin>

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

Issue Links

Activity

Hide
Grégory Joseph added a comment -

(using site-plugin-2.0-beta-4)

Show
Grégory Joseph added a comment - (using site-plugin-2.0-beta-4)
Hide
Brett Porter added a comment -

is it because of inheritence (MNG-1999)?

This works for me.

Show
Brett Porter added a comment - is it because of inheritence (MNG-1999)? This works for me.
Hide
Grégory Joseph added a comment -

Nope, this project is standalone, no inheritence involved.
I could attach my complete pom next monday, but I'm not sure how much it'd help since many dependencies will not be available outside of my company's repo..

Show
Grégory Joseph added a comment - Nope, this project is standalone, no inheritence involved. I could attach my complete pom next monday, but I'm not sure how much it'd help since many dependencies will not be available outside of my company's repo..
Hide
Jean Deruelle added a comment -

move to maven-2-0-4 (it's using site-plugin-2.0-beta-5). Looks like the inital problem you had(problems when generating the dependencies report due to m1 dependencies) is fixed.

Show
Jean Deruelle added a comment - move to maven-2-0-4 (it's using site-plugin-2.0-beta-5). Looks like the inital problem you had(problems when generating the dependencies report due to m1 dependencies) is fixed.
Hide
Max Bowsher added a comment -

Does <reporting><excludeDefaults>true</excludeDefaults></reporting> work at all?

If I run "mvn help:effective-pom" on a project containing it, it is not present in the effective-pom output, suggesting that it never got parsed properly in the first place.

Show
Max Bowsher added a comment - Does <reporting><excludeDefaults>true</excludeDefaults></reporting> work at all? If I run "mvn help:effective-pom" on a project containing it, it is not present in the effective-pom output, suggesting that it never got parsed properly in the first place.
Hide
Milos Kleint added a comment -

doesn't work for me either. using maven 2.0.7 and whatever the current latest site plugin is.

Show
Milos Kleint added a comment - doesn't work for me either. using maven 2.0.7 and whatever the current latest site plugin is.
Hide
Dennis Lundberg added a comment -

I tried this and here are my findings:

  • <excludeDefaults> only removes the "Project Information" menu from the site, but still creates the reports
  • <reportSets> does not create the reports and does not add the "Project Information" menu to the site

These tests were done using Maven 2.0.7 and maven-site-plugin 2.0-beta-4.

Show
Dennis Lundberg added a comment - I tried this and here are my findings:
  • <excludeDefaults> only removes the "Project Information" menu from the site, but still creates the reports
  • <reportSets> does not create the reports and does not add the "Project Information" menu to the site
These tests were done using Maven 2.0.7 and maven-site-plugin 2.0-beta-4.
Hide
Dennis Lundberg added a comment -

Seems to have something to do with reading the pom.

Show
Dennis Lundberg added a comment - Seems to have something to do with reading the pom.
Hide
Benjamin Bentmann added a comment -

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.

Show
Benjamin Bentmann added a comment - 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.
Hide
Benjamin Bentmann added a comment -

Fixed by Brett in r705567 and r705574, respectively.

Show
Benjamin Bentmann added a comment - Fixed by Brett in r705567 and r705574, respectively.

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: