[
http://jira.codehaus.org/browse/MASSEMBLY-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160514#action_160514
]
John Casey commented on MASSEMBLY-115:
--------------------------------------
We need to verify whether unforced (i.e. update functionality?) works for the
archivers provided by plexus-archiver...I don't think we can take that for
granted, definitely.
> 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
>
> Attachments: massembly-115.patch
>
>
> 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
