[
http://jira.codehaus.org/browse/MNG-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201746#action_201746
]
Tamás Cservenák commented on MNG-4368:
--------------------------------------
Paul, you are missing the point. I created this SVN example project only to
present the problem.
What I wanted to emphasize, that today, when Git (and DSCM-s in general) are
more and more widely accepted, a projectX may exist in multitude of Git reposes
out there. None of them are "mine" (are governed by me), so i cannot
"manage"/control what version they use when forked a git repository.
My point is, that the "best practice" of having _distinct version_ (or better
G:A:V) per branch works nicely with centralized SCMs like CVS/SVN. But hardly
with any DSCM.
The case that happened to me was exactly the same: had built _same_ project's
different branches, coming from _different Git reposes_ (but the different Git
reposes were mirroring _same_ master SVN repo!).
> 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
