[
https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561713#comment-17561713
]
Herve Boutemy edited comment on MSHARED-480 at 7/2/22 6:39 AM:
---------------------------------------------------------------
yes, let's stop trying to make a standalone report mojo look like if it was
done part of a site: standalone is standalone
having a standalone-oriented output will clarify many things, and finally
improve user experience
in fact, this issue should be superceeded by another defining the standalone
report look and feel
was (Author: hboutemy):
yes, let's stop trying to make a standalone report mojo look like if it was
done part of a site: standalone is standalone
having a standalone-oriented output will clarify many things, and finally
improve user experience
in fact, this issue should be reoriented toward defining the standalone report
look and feel
> 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
> 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)
