[jira] [Commented] (MNG-7802) Fix behaviour of the maven update policy

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on MNG-7802:
-------------------------------------

cstamas commented on PR #1144:
URL: https://github.com/apache/maven/pull/1144#issuecomment-1663893897

   To be done in resolver 2.0.0, please once out upgrade to this instead https://issues.apache.org/jira/browse/MRESOLVER-377




> Fix behaviour of the maven update policy
> ----------------------------------------
>
>                 Key: MNG-7802
>                 URL: https://issues.apache.org/jira/browse/MNG-7802
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.x-candidate
>
>
> The update policy can be specified using the {{-U}} (force update) or {{-nsu}} (no update) options, but those options change the whole repository session policy and override any settings on the repositories.
> This means that if {{-U}} is set, the resolver will attempt to check already downloaded artifacts.  This is wrong and the behaviour has been inherited from maven 2.x.
> What we really wants (and what's implied by the name of the options and docs) is to check for new artifacts / updates, so this mainly affect _version resolution_ and not {_}artifact resolution{_}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)