[MSHARED-1099] Render with a skin when report is run in standalone mode

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: maven-reporting-impl-4.0.0-M2, maven-reporting-impl-3.2.0, maven-reporting-impl-4.0.0
• Component/s: maven-reporting-impl
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 03/Jul/22 20:17
• Updated: 14/Dec/23 16:55
• Resolved: 06/Aug/22 21:48

Description

Currently, when a report is run in standalone mode the default skin is always applied. This causes several problems:

• It is always tied to the Doxia Sitetools version
• The default skin cannot be removed
• Another skin cannot be used

The improvement is to fully utilize skins from repos just like Maven Site Plugin does and provide a default skin: org.apache.maven.skins:maven-fluido-skin:1.11.1. This can always be overriden on a per-plugin basis. Completely decoupled from the Maven Site Plugin since it does not use site.xml. For skin developers, a standalone == true (Boolean) attribute will be added to the template properties to switch between site and standalone mode.

Issue Links

• fixes: MPIR-423 dependencies goal doesn't create required resources
• is depended upon by: MSKINS-202 Support Maven report standalone mode
• relates to: MPIR-423 dependencies goal doesn't create required resources
• requires: MPIR-422 Stop overriding AbstractMavenReport#execute()
• links to: GitHub Pull Request #9