[
https://issues.apache.org/jira/browse/MSITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247058#comment-16247058
]
Hervé Boutemy commented on MSITE-802:
-------------------------------------
did you try to generate markup to {{generatedSite}} = {{target/generated-site}}
instead?
see
http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#generatedSiteDirectory
This is the location where generated markup is expected to be put ({{src/*}} is
not supposed to be modified by the build process, only {{target/*}}
> Support more than one directory
> -------------------------------
>
> Key: MSITE-802
> URL: https://issues.apache.org/jira/browse/MSITE-802
> Project: Maven Site Plugin
> Issue Type: New Feature
> Reporter: Allen Wittenauer
> Priority: Minor
>
> 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)
