[MNG-4162] Removal of all reporting logic from the core of Maven

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0-beta-1
• Assignee: Benjamin Bentmann
• Reporter: Jason van Zyl
• Created: 16/May/09 09:43
• Updated: 21/Jun/22 05:58
• Resolved: 25/Mar/10 17:01

Description

Any reporting implementation will be implemented as a plugin. Maven will provide any information, APIs, and extension points to make this possible. But the conflation of building with reporting in the core makes it almost impossible for anyone to understand the distinction, makes it impossible to have alternate implementations and couple many tools like Doxia directly to the core which is unacceptable for Maven 3.x.

Issue Links

• causes: MNG-7504 Warning about unknown reportPlugins parameters for m-site-p are always generated
• is related to: MNG-6189 WARN if maven-site-plugin configuration contains reportPlugins element
• is related to: MNG-7408 Explain reporting plugin version automatic selection (in Maven 3)
• is related to: MNG-7505 Remove ReportingConverter
• is related to: MSHARED-628 support maven-model ReportPlugin in addition to local copy
• is related to: MSITE-792 drop reportPlugins parameter ("new format")
• is related to: MPIR-174 remove use of container.getLoggerManager() (to be compatible wih maven 3.x)
• is related to: MSITE-484 Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
• relates to: MNG-4261 site plugin doesn't generate reports

Sub-Tasks

• Deprecate all methods in MavenProject that relate to reporting.: Closed