The following comment has been added to this issue:
Author: Colin Saxton
Created: Tue, 13 Jul 2004 8:17 AM
Body:
This is useful when you are writing large builds since you continually chop and change
component maven/pom/src to make sure everything is working fine...in some cases you
don't want to do a full install/build you just want to test your changes so it
wouldn't make sense at that point to do a clean and then a build. That decision should
really be in the hands of the developer.
I could understand if this was a complicated update but its just a simple deletion on
one line.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJAR-33?page=comments#action_21715
---------------------------------------------------------------------
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
Versions:
1.6
Assignee: Jason van Zyl
Reporter: Colin Saxton
Created: Tue, 13 Jul 2004 4:30 AM
Updated: Tue, 13 Jul 2004 8:17 AM
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
