[jira] [Reopened] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov reopened MSHARED-480:
------------------------------------
      Assignee: Michael Osipov

Reopening for the moment since I found a non-too-intrusive way to solve this problem. Will share a possible solution next after Doxia Sitetools 2.0.0-M4 release.

> use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo
> ---------------------------------------------------------------------------------------
>
>                 Key: MSHARED-480
>                 URL: https://issues.apache.org/jira/browse/MSHARED-480
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-reporting-impl
>    Affects Versions: maven-reporting-impl 2.4
>            Reporter: Herve Boutemy
>            Assignee: Michael Osipov
>            Priority: Minor
>
> currently, when a reporting mojo is not used as maven-site-plugin's report but as direct mojo invocation, maven-site-renderer default skin is always used: would be more consistent if using site decoration consistently with maven-site-plugin
> Or more precisely, I didn't currently find any reporting plugin that did the effort to mimic maven-site-plugin's decoration model/skin: every reporting plugin I know of uses features of {{maven-reporting-impl}} for site rendring (with this known limitation)
> implementing the feature in {{maven-reporting-impl}} will make it accessible to any reporting plugin once it upgrades it dependency version
> once done, we can activate skin resources copy, that was commented while working on MSHARED-120 (and would not give expected result if skin used is not consistent)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)