[
https://issues.apache.org/jira/browse/MNG-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532971#comment-17532971
]
Tamás Cservenák edited comment on MNG-6806 at 5/6/22 4:34 PM:
--------------------------------------------------------------
I agree, but: I also consider that resolver should be "in lockstep" with maven
artifacts as well, as they should be also "versions that work together". Today,
maven core "contributes" the resolver api, spi and impl, while plugins "bring
their own" resolver util and connector, that is IMHO sub optimal (it may cause
not only minor but even major differences across 5 artifacts).
was (Author: cstamas):
I agree, but: I also consider that resolver should be "in lockstep" with maven
artifacts as well, as they should be also "versions that work together". Today,
maven core "contributes" the resolver api, spi and impl, while plugins "bring
their own" resolver util and impl, that is IMHO sub optimal (it may cause not
only minor but even major differences across 5 artifacts).
> Provide Maven BOM
> -----------------
>
> Key: MNG-6806
> URL: https://issues.apache.org/jira/browse/MNG-6806
> Project: Maven
> Issue Type: Improvement
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> Maven libraries should always have the same version to ensure they work as
> expected, hence the preferred way to manage that is with a bom.
> Let's introduce the {{maven-dependencies}}, a
> [bom|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]
> for Maven dependencies. We will likely need the same for plugins.
> See https://www.baeldung.com/spring-maven-bom about how to write and use the
> bom.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
