[
http://jira.codehaus.org/browse/MNG-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201968#action_201968
]
Tamás Cservenák commented on MNG-4368:
--------------------------------------
IMO, the proper fix would be, to handle POMs always _as POMs_. So, as
_metadata_, and _always_ install them (to not apply the fix in this issue to
them). The main problem I see here, is that Maven handles POM as "artifact to
install" (when packaging is "pom"), and sometimes as "repository metadata"
(when packaging is not "pom"). Clearly, this fix does bring value for JARs,
EARs, WARs, etc, but they are _built_/_assembled_ then installed (and will be
newer than the one in local repository), but in case of "installing POM as main
artifact" we have a plain file copy happening, with file that is potentially
_older_ than the already in local repository.
> 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
