[MASSEMBLY-115] Should avoid modifying assembly if none of the underlying files have changed.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2
• Assignee: John Dennis Casey
• Reporter: David Boden
• Created: 12/Jun/06 04:45
• Updated: 28/Sep/10 15:28
• Resolved: 23/Sep/10 14:15

Description

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.

Issue Links

• is duplicated by: MASSEMBLY-402 Assembly plugin goals should have a forceCreation parameter.