[
http://jira.codehaus.org/browse/MSITE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215307#action_215307
]
Anthony Whitford commented on MSITE-250:
----------------------------------------
My use case is that I deploy the site files to a file share: {{\\server\sites}}
The sites are organized by project and version:
{{\\server\sites\project\version}}
The CI server will build the site, let's say for {{1.0-SNAPSHOT}}:
{{\\server\sites\project\1.0-SNAPSHOT\}}
Then, I will release this project, and I get a site for {{1.0}}:
{{\\server\sites\project\1.0\}}
My issue is that I am getting _toxic waste buildup_ by not removing the old
{{1.0-SNAPSHOT}} directory.
If I had a {{site:clean}} goal, I could build it into my release workflow.
Better yet, the release plugin could leverage it and automatically purge the
old snapshot files.
> Allow cleaning of the remote area or staging site
> -------------------------------------------------
>
> Key: MSITE-250
> URL: http://jira.codehaus.org/browse/MSITE-250
> Project: Maven 2.x Site Plugin
> Issue Type: New Feature
> Reporter: Wim Deblauwe
>
> When files have been removed, they are not removed from the remote deploy
> area or the staging site. A new goal to clean the staging or the final deploy
> area would be a nice addon to this plugin.
--
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
