[ https://issues.apache.org/jira/browse/MSHARED-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MSHARED-1099: ------------------------------------ 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. was: 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 switch between site and standalone mode. > Render with a skin when report is run in standalone mode > -------------------------------------------------------- > > Key: MSHARED-1099 > URL: https://issues.apache.org/jira/browse/MSHARED-1099 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-reporting-impl > Reporter: Michael Osipov > Assignee: Michael Osipov > Priority: Major > Fix For: maven-reporting-impl-4.0.0-M2 > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)