You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Christoforides (JIRA)" <ji...@codehaus.org> on 2007/11/28 22:34:57 UTC
[jira] Commented: (MASSEMBLY-115) Should avoid modifying assembly
if none of the underlying files have changed.
[ http://jira.codehaus.org/browse/MASSEMBLY-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115289 ]
Andreas Christoforides commented on MASSEMBLY-115:
--------------------------------------------------
The current behavior of the assembly plugin considerably slows down the build time of projects that rely heavily on assemblies. I am currently working on a multimodule project that generates many artifacts using assemblies. Even with no changes to any source code the build takes a lot longer since it needs to zip and war a lot of files every time. The JAR and WAR plugins have the ability to check for modifications and build an artifact only if they were changes. It would be nice for the assembly plugin to behave in similar way.
> Should avoid modifying assembly if none of the underlying files have changed.
> -----------------------------------------------------------------------------
>
> Key: MASSEMBLY-115
> URL: http://jira.codehaus.org/browse/MASSEMBLY-115
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Reporter: David Boden
> Fix For: 2.3-beta-1
>
>
> At the moment, the assembly plugin always generates a the specified bundle, no matter whether or not the files to be placed in the bundle are changed.
> This means that any plugins downstream (e.g. you want to digitally sign the bundle) behave as if a "clean" has taken place.
> It would be better if the assembly plugin did not build a bundle if it is going to be the same as what was produced during the last build. That way, the last modified timestamp of the bundle won't get updated, and the downstream plugins will know that nothing has changed.
> Adding an assembly to a build currently slows down the iterative "install" build very significantly because of this issue. Clean builds are not effected by this issue, but effectively the assembly is forcing a clean build every time.
--
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