[
http://jira.codehaus.org/browse/MNG-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201890#action_201890
]
Ralph Goers commented on MNG-4368:
----------------------------------
My 2 cents.
"I don't believe changing the version within your POM is an unnecessary burden.
It sounds reasonable and smart to do so no matter how short or long your branch
lives."
Yes, it is. Quite often developers work on their own branches to add some
feature that will then be integrated back to main. This is expecially true with
git. Requiring them to change versions makes merging that much harder.
Furthermore, taking the attitude that the Maven developers know best how other
developers should work usually leads to resentment and people coming to dislike
the tool.
> 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
