[
https://issues.apache.org/jira/browse/MNG-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-7802:
---------------------------------
Description:
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{_}.
was:
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{_}.
Also, the CLI options for {{-U}} and {{-nsu}} indicates that those are for
snapshots, while they actually affect all policies, so those should be renamed
and their doc fixed.
> Fix behaviour of the maven update policy
> ----------------------------------------
>
> Key: MNG-7802
> URL: https://issues.apache.org/jira/browse/MNG-7802
> Project: Maven
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
>
> 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)
