[
http://jira.codehaus.org/browse/MSITE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-361.
-------------------------------
Resolution: Won't Fix
Assignee: Lukas Theussl
Only the final generated site in target/site should get deployed by both deploy
and stage-deploy. If you don't want some files to be included, make sure they
don't get generated in there (if a plugin generates temporary files in
target/site, this should be considered a bug, cobertura generates its files in
target/cobertura, not target/site/cobertura).
> Site:stage should have file include/exclude options
> ---------------------------------------------------
>
> Key: MSITE-361
> URL: http://jira.codehaus.org/browse/MSITE-361
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Improvement
> Components: site:deploy, site:stage(-deploy)
> Affects Versions: 2.0-beta-6
> Environment: JDK 1.5 for Windows
> Reporter: Ben Speiser
> Assignee: Lukas Theussl
>
> The site:stage goal moves a set of files that are designated as generated
> content to the staging area. However, this doesn't provide any flexibility
> to include additional generated content or exclude certain generated
> content, such as generated Cobertura XML files. The Maven Site Plugin should
> have an option to configure additional includes and excludes for when content
> is staged. Presumably, site:deploy and site:stage-deploy have the same
> problem; although I have not tested it. Certainly no include/exclude options
> are present in the plugin documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
