Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.6
-
None
-
None
Description
waiting for MSITE-484 that is a strong prerequisite, it's better to simply drop this reportPlugins parameter that requires extra code in Maven core and clutters effective pom (reporting section is copied to maven-site-plugin configuration)
Once reportPlugins parameter is removed, it shows again clearly that the only way to configure reports is by filling reporting section
Maven 3.5.0 is already warning if a pom.xml contains a reference to this reportPlugins parameter MNG-6189: this is only the beginning of the removal of this currently failed feature
Attachments
Issue Links
- breaks
-
MSITE-806 Site generation does not work when no report configured nor Doxia document provided
- Closed
- causes
-
MNG-7504 Warning about unknown reportPlugins parameters for m-site-p are always generated
- Closed
- depends upon
-
MSHARED-628 support maven-model ReportPlugin in addition to local copy
- Closed
- is related to
-
MPDF-48 make PDF plugin run reports when used with Maven 3
- Closed
- relates to
-
MSITE-484 Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
- Closed
-
MPMD-128 Xref link generation regression with Maven 3
- Closed
-
MNG-4162 Removal of all reporting logic from the core of Maven
- Closed
-
MNG-6189 WARN if maven-site-plugin configuration contains reportPlugins element
- Closed
-
MNG-5463 warn if maven-site-plugin's reportPlugins is configured in POM
- Closed