[
http://jira.codehaus.org/browse/MNG-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201618#action_201618
]
Tamás Cservenák commented on MNG-4368:
--------------------------------------
The fact is, that I did full rebuild, and was completely puzzled after T2 why
my build fails with - well, let's say "strange" at least - error. All three
builds (T0, T1 and T2) were full builds.
And as I noted the same thing on MavenDev list: if maven "best practice"
requires you to have _different_ version on _every existing branch_, how this
fit Git or any other Distributed SCM? Who will coordinate these versions, that
may exist in multiple Git repositories out there?
> 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
