[
https://issues.apache.org/jira/browse/MSITE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065618#comment-15065618
]
Hervé Boutemy commented on MSITE-690:
-------------------------------------
FYI, that's not exactly how it is done: content generated by a report plugin is
immediately merged to the skin/template through
[doxia-site-renderer|http://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/doxia-site-renderer/]
but IIUC the issue you're facing, it's about {{mvn clean
checkstyle:checkstyle-aggregator}} not rendering decent HTML: ok, this is a use
case when a reporting plugin is not used as report (run by m-site-p) but it is
run as normal plugin/mojo
[maven-reporting-impl|http://maven.apache.org/shared/maven-reporting-impl/] is
a base implementation of this behaviour, that should probably be enhanced to
generate better HTML when used as mojo: I know that the code regarding skinning
in this case is very basic, since it does not try to get site's decoration
model. But I did have higher priorities until now: perhaps it is a good time to
rework on it, if you're interested
notice that once the component is updated, every reporting plugin will have to
upgrade to benefit from the enhanced "run report as mojo" behaviour
> Add new "process-reports" goal
> ------------------------------
>
> Key: MSITE-690
> URL: https://issues.apache.org/jira/browse/MSITE-690
> Project: Maven Site Plugin
> Issue Type: Improvement
> Affects Versions: 3.3
> Reporter: scolebourne2
>
> AFAICT, maven builds a site by relying on other plugins to generate files in
> a specific HTML format. For example, the PMD and Checkstyle plugins generate
> reports that include references to {{@import url("./css/maven-base.css");}}
> and "$\{project.version}". The site plugin then post-processes these files to
> do three things:
> (a) add the css files,
> (b) convert references like $\{project.version}
> (c) add in a generated menu structure with relative links
> Propose adding a new goal "process-reports" that performs steps (a) and (b)
> only. Instead of generating the index structure in step (c), it would simply
> remove the index and header parts of the HTML file to create a simple
> *standalone* HTML file.
> The aim of this improvement is to allow valid complete HTML files to be
> created without the rest of the generated site (with the complications of
> relative links). This goal would simply run in each project of the
> multi-module build independently, processing the resources it finds locally.
> Users wanting a checkstyle report could then run "mvn clean
> checkstyle:checkstyle-aggregator site:process-reports". Today, "mvn clean
> checkstyle:checkstyle-aggregator" works OK but produces half-complete HTML
> files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
