[jira] Updated: (MPJAR-33) jar:install copies jar even when no changes have occurred

["Jason van Zyl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MPJAR-33?page=all ]

Jason van Zyl updated MPJAR-33:
-------------------------------

    Assign To:     (was: Jason van Zyl)

> jar:install copies jar even when no changes have occurred
> ---------------------------------------------------------
>
>          Key: MPJAR-33
>          URL: http://jira.codehaus.org/browse/MPJAR-33
>      Project: maven-jar-plugin
>         Type: Improvement

>     Versions: 1.6
>  Environment: Linux/Windows
>     Reporter: Colin Saxton

>
> Original Estimate: 2 minutes
>         Remaining: 2 minutes
>
> jar:install copies the built jar from the target area to the local repository even if the jar has no changes. This can cause a snowball effect on builds if you are using the reactor for instance. When testing a large project (before a release) it can be cumbersome since the build time is increased significantly.
> As an example, I currently use the reactor to build 26 separate jars with all of them dependent on the base component. if I change one of them and then re-run the build it builds everything because the base jar is being copied back into the repository even if I don' change it. This causes the reactor to build all of the other jars and so-forth.
> All that is needed is to change the jar:install copy line...remove the overwrite attribute and the builds speed up...It doesn't break anything either since you can alway runs a clean before a major build but when testing you can just keep running maven without the clean...you would be saving a lot of disk activity around the world by removing the overwrite attribute.

-- 
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