You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/03/21 16:43:00 UTC

[jira] [Closed] (MNG-6806) Provide Maven BOM

     [ https://issues.apache.org/jira/browse/MNG-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MNG-6806.
-------------------------------
    Fix Version/s:     (was: 4.0.x-candidate)
                   4.0.0-alpha-1
                   4.0.0
         Assignee: Robert Scholte
       Resolution: Fixed

Fixed in [3e656376e8271d839c99de3d0ae2746c593e7daa|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=3e656376e8271d839c99de3d0ae2746c593e7daa]

> 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
>              Labels: up-for-grabs
>             Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> 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.3.4#803005)