[
https://issues.apache.org/jira/browse/MSITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254946#comment-16254946
]
Hervé Boutemy commented on MSITE-802:
-------------------------------------
thanks for the example: it's a report without taking time to create a report
plugin :)
notice reading shelldocs documentation, it looks like it directly generates
HTML (which could directly go to target/site), but in your snippet, it
generates Markdown and let the user find a tool to translate Markdown to html
(that's why Markdown has to go into target/generated-site/markdown, to let
maven-site-plugin translate it to html with site's Maven skin)
I think I'll add a section in
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
on "Generating Content" that will introduce the different ways to generate
content
in fact, I think this will cover a long overdue documentation: how to create a
reporting plugin?
Interesting and useful, but more complex
We're driving a new maven-site-plugin release soon for Java 9 compatibility, I
need to work on this soon...
> Support more than one directory
> -------------------------------
>
> Key: MSITE-802
> URL: https://issues.apache.org/jira/browse/MSITE-802
> Project: Maven Site Plugin
> Issue Type: Task
> Reporter: Allen Wittenauer
> Assignee: Hervé Boutemy
> Priority: Minor
> Fix For: 3.7
>
>
> It would be great if maven-site-plugin could support more than one site
> directory per module. Specifically, I'm looking for a way to process
> generated content without copying all of src/site into target where my
> generated content is sitting or using a separate module that only handles
> generated content to get aggregated later.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
