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

[ji...@codehaus.org]

The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Fri, 15 Oct 2004 8:42 PM
    Changes:
             Fix Version changed to 1.7
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPJAR-33?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPJAR-33

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPJAR-33
    Summary: jar:install copies jar even when no changes have occurred
       Type: Improvement

     Status: Open
   Priority: Major

 Original Estimate: 2 minutes
 Time Spent: Unknown
  Remaining: 2 minutes

    Project: maven-jar-plugin
   Fix Fors:
             1.7
   Versions:
             1.6

   Assignee: Jason van Zyl
   Reporter: Colin Saxton

    Created: Tue, 13 Jul 2004 4:30 AM
    Updated: Fri, 15 Oct 2004 8:42 PM
Environment: Linux/Windows

Description:
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. 


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org