I fixed this issue in r808537 in 3.0 trunk and r808535 in 2.2.x.
I note that I fixed this in DefaultArtifactInstaller, which now lives in
maven-compat, suggesting that it has been deprecated for the future...?
Is there some similar code that needs to be updated in Mercury?
-Dan
Dan Fabulich wrote:
http://jira.codehaus.org/browse/MARTIFACT-19
DefaultArtifactInstaller should only overwrite files if timestamp has changed
This bug seems really bad for performance in large reactor builds or even
just for builds with large jars/wars/assemblies. The fix appears to be a
one-line fix.
I'm surprised it's gone this long without being noticed... Is there some
non-obvious reason not to do this?
I think I'm going to just check in the change in maven-2/branches/maven-2.2.x
and repeat the change in trunk sometime tomorrow unless somebody objects.
(It results in a nice pick-me-up on my machine...)
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org