[
http://jira.codehaus.org/browse/MNG-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201617#action_201617
]
Brett Porter edited comment on MNG-4368 at 12/7/09 4:16 PM:
------------------------------------------------------------
Even if this is reverted, the above will run into problems if you don't do a
complete rebuild every time you switch branches. I would advocate renaming the
version on your branches (using the versions plugin, or created with
release:branch, for example), if they are not actually the same development
version of things.
However, an option to force installation would be a helpful thing to add.
was (Author: brettporter):
Even if this is reverted, the above will run into problems if you don't do
a complete rebuild every time you switch branches. I would advocate renaming
the version on your branches (using the versions plugin, or created with
release:branch, for example), if they are not actually the same development
version of things.
> DefaultArtifactInstaller should only overwrite files if timestamp has changed
> -----------------------------------------------------------------------------
>
> Key: MNG-4368
> URL: http://jira.codehaus.org/browse/MNG-4368
> 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 process.
--
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
