You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/02/23 11:08:00 UTC
[jira] [Resolved] (MNG-8019) Streamline update policy of pluginRepository/repository of Maven Central in Super POM
[ https://issues.apache.org/jira/browse/MNG-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved MNG-8019.
----------------------------------
Fix Version/s: 3.9.7
(was: 3.9.x-candidate)
Resolution: Fixed
Fixed in https://github.com/apache/maven/commit/9a84fdf2a9502956599c01d740b934b631550701.
> Streamline update policy of pluginRepository/repository of Maven Central in Super POM
> -------------------------------------------------------------------------------------
>
> Key: MNG-8019
> URL: https://issues.apache.org/jira/browse/MNG-8019
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.9.7
>
>
> The update policy is set to {{never}} for the Maven Central {{pluginRepository}} (https://github.com/apache/maven/blob/b23afbc9849d57b0a4ff0f2bdd3fff5520a95f7c/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml#L48) while it is the default (= {{daily}}) for the regular repository.
> Although it would be nice to set both to {{never}} this does not work with Resolver 1.x as that treats metadata and artifacts the same (but in fact metadata is constantly changing even for release repositories like Maven Central). This situation should improve with Resolver 2.x (Maven 4) (https://issues.apache.org/jira/browse/MRESOLVER-377).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)