[jira] [Commented] (MNG-5428) Update documentation to make it clear released artifacts are *never* updated in the local cache

["Michael Osipov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073320#comment-15073320 ] 

Michael Osipov commented on MNG-5428:
-------------------------------------

Just to make it clear, update policy for snapshots applies for files and metadata and for releases to metadata only? This is how I understood Stephen's answer.

> Update documentation to make it clear released artifacts are *never* updated in the local cache
> -----------------------------------------------------------------------------------------------
>
>                 Key: MNG-5428
>                 URL: https://issues.apache.org/jira/browse/MNG-5428
>             Project: Maven
>          Issue Type: Improvement
>          Components: Documentation:  General
>    Affects Versions: 3.3.9
>            Reporter: Kent Moore
>            Priority: Minor
>              Labels: close-pending
>
> A literal reading of the "updatePolicy" section of http://maven.apache.org/ref/3.0.4/maven-settings/settings.html, as well as  Maven help for the "-U" option, makes it seem as though Maven is capable of updating release artifacts in the local cache.  But that is not the case.
> I believe the documentation in both areas should be updated to make it clear released artifacts are *never* re-downloaded to the local Maven cache, even if the repository manager contains a newer version of the release (which shouldn't ever happen, but....).
> See http://mail-archives.apache.org/mod_mbox/maven-users/201301.mbox/%3CCANdpH_0qHU5grD%3D%3DPRWDJiU7YFsoqw8T0Az0XTJRD7%3DOtwMjtw%40mail.gmail.com%3E.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)