Maven 2.x and 3.x Site Plugin

inheritedReports IT fails

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.0-beta-3
  • Fix Version/s: None
  • Component/s: inheritance, Maven 3
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    0

Description

as discovered in MSITE-595:

  • with M2, each report is added: child has 2 reports generated = index+summary
  • with M3, each report replaces previous one: child has 1 report = summary

What is the expected behaviour? I'd say M2 is buggy, since POM inheritance logic usually replaces instead adding
Should we try to stick with M2 behaviour? (if feasible, I still didn't check)

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MNG-5155 'inherited' flag of report sets ignored.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MSITE-484 Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Bug - A problem which impairs or prevents the functions of the product. MSITE-595 inheritedMenus IT fails

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MSITE-686 Report inheritance does not work as specified

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Herve Boutemy added a comment -

to have the same behaviour in M3 than in M2, we need a new Maven version: see ModelMerger#mergeReporting_Plugins() which is not overrided in MavenModelMerger

and of course, this can't be done in the new format, since inheritance is not supported at all

Show
Herve Boutemy added a comment - to have the same behaviour in M3 than in M2, we need a new Maven version: see ModelMerger#mergeReporting_Plugins() which is not overrided in MavenModelMerger and of course, this can't be done in the new format, since inheritance is not supported at all
Hide
Permalink
Lukas Theussl added a comment -

If this cannot get fixed for 3.1, we need to document the different behaviour.

Show
Lukas Theussl added a comment - If this cannot get fixed for 3.1, we need to document the different behaviour.
Hide
Permalink
Karl M. Davis added a comment -

Please note that some folks (me, for example) are now relying on the Maven 3 behavior to exclude reports in child projects. If you change this behavior, a number of my projects would break as I need a way to exclude reports occasionally.

Show
Karl M. Davis added a comment - Please note that some folks (me, for example) are now relying on the Maven 3 behavior to exclude reports in child projects. If you change this behavior, a number of my projects would break as I need a way to exclude reports occasionally.
Hide
Permalink
Herve Boutemy added a comment -

fixed as a side effect of MNG-5155: Maven 3.0.4 and later have the same behaviour than Maven 2

IT modified in consequence in r1480782

Show
Herve Boutemy added a comment - fixed as a side effect of MNG-5155 : Maven 3.0.4 and later have the same behaviour than Maven 2 IT modified in consequence in r1480782

People

  • Assignee:
    Herve Boutemy
    Reporter:
    Herve Boutemy
Vote (2)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: