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

[jira-importer]

Michael Osipov opened MSHARED-1099 and commented

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:

• MPIR-423 dependencies goal doesn't create required resources
  ("fixes")

• MPIR-423 dependencies goal doesn't create required resources

• MPIR-422 Stop overriding AbstractMavenReport#execute()
  ("requires")

• MSKINS-202 Support Maven report standalone mode
  ("is depended upon by")

Remote Links:

• GitHub Pull Request #9
  

Backported to: maven-reporting-impl-3.2.0

[jira-importer]

Michael Osipov commented

Fixed with 4a1539e2117dc34f9ad3f0e4fc0bd738bb9d3881.

[jira-importer]

Michael Osipov commented

Fixed with ecf1b039a76a1b6eeda5e79e0885599e9e573cc8 for maven-reporting-impl-3.x branch.