[
http://jira.codehaus.org/browse/MWAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121170
]
Michele Lorenzini commented on MWAR-138:
----------------------------------------
Ok, I did not considered the need for optimiziation in multiple builds.
It is actually more important than cleanup.
Thanks.
> Cleanup of war/work after war overlay
> -------------------------------------
>
> Key: MWAR-138
> URL: http://jira.codehaus.org/browse/MWAR-138
> Project: Maven 2.x War Plugin
> Issue Type: Improvement
> Affects Versions: 2.1-alpha-1
> Reporter: Michele Lorenzini
> Assignee: Stephane Nicoll
> Priority: Minor
>
> I'm using war overlay to build a final war application from many other war
> projects which overlays in the final artifact.
> I've noticed the overlay mechanism uses a working dir (target/war/work) where
> all wars are copied before being overlaid on the target war.
> This folder is left there after the build.
> This folder can become a little big after a build, so I think there should be
> a way to handle the cleanup of this working folder after that.
> I think it should be deleted automatically by default after the overlay has
> finished, maybe with an option to disable the cleanup, which can be
> useful if I need to "see" what the plugin is overlaying.
> I know that a mvn clean will also cleanup this, but it will also cleanup the
> final build of the artifact.
> As an example, I have a scenario where a base war project has the most of the
> files used by the final war.
> This is also used by all the war submodules so I can build and run each
> module indipendently, in this way each war output is similar to others in size
> (say around 15MB).
> When I build the final war overlaying all of these wars (producing a final
> war of say 20MB) I have a war/work folder which is 15M x N where N is the
> numbre of submodules (I have a dozen of them at now but can be more in the
> future, coming in a waste of disk space in the target folder after each
> build).
--
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
