[ 
https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643765#comment-17643765
 ] 

Michael Osipov edited comment on MSHARED-480 at 12/6/22 9:54 AM:
-----------------------------------------------------------------

Here is a solution to the issue:
1. Build from 
https://github.com/apache/maven-reporting-impl/compare/master...use-site.xml 
and install
2. Build from 
https://github.com/apache/maven-project-info-reports-plugin/compare/doxia-2.0.0...use-site.xml
 and try

[~hboutemy], I am not fully happy with 
https://github.com/apache/maven-project-info-reports-plugin/compare/doxia-2.0.0...use-site.xml#diff-7f69e35571e6f28056ef79ea1930349d407b4ccd405a2c75e45ba3e6e47a8430R188-R194,
 maybe you have a better idea for this test config snippet.


was (Author: michael-o):
Here is a solution the issue:
1. Build from 
https://github.com/apache/maven-reporting-impl/compare/master...use-site.xml 
and install
2. Build from 
https://github.com/apache/maven-project-info-reports-plugin/compare/doxia-2.0.0...use-site.xml
 and try

[~hboutemy], I am not fully happy with 
https://github.com/apache/maven-project-info-reports-plugin/compare/doxia-2.0.0...use-site.xml#diff-7f69e35571e6f28056ef79ea1930349d407b4ccd405a2c75e45ba3e6e47a8430R188-R194,
 maybe you have a better idea for this test config snippet.

> 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: Improvement
>          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)

Reply via email to