maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Basil James Whitehouse III (JIRA)" <>
Subject [jira] Commented: (MNG-4368) DefaultArtifactInstaller should only overwrite files if timestamp has changed
Date Wed, 09 Dec 2009 00:44:55 GMT


Basil James Whitehouse III commented on MNG-4368:

I frequently have a similar workflow as Tamás, in my case with short lived bug branches (less
than a week) that get incorporated back into the trunk/mainline.  I feel the proposed flow
to change the version number would expand the workflow unnecessarily.  Note that these branches
aren't used by other developers, merely as a location for me to commit, test, refactor, and
reintegrate with the mainline when ready.  I run clean install before integrating to ensure
the branch and trunk is buildable.  I have used the versions plugin and it's very useful,
but in this case the flow works well (in Maven 2.2.1) without requiring me to switch the version
when I create the branch, and switch it back when I merge into the mainline.

> DefaultArtifactInstaller should only overwrite files if timestamp has changed
> -----------------------------------------------------------------------------
>                 Key: MNG-4368
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>         Environment: Linux, JDK 1.5
>            Reporter: Johannes Martin
>             Fix For: 2.2.2, 3.0-alpha-3
> install:install (from maven-install-plugin) by default uses DefaultArtifactInstaller
to install artifacts. DefaultArtifactInstaller in turn uses FileUtils.copyFile(), thereby
overwriting destination files even if they are unchanged. It would be helpful if DefaultArtifactInstaller
used FileUtils.copyFileIfModified() instead, at least as an option, to speed up the build

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message