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

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2020/10/28 11:08:00 UTC

[jira] [Updated] (MENFORCER-360) requireUpperBoundDeps should have option to check for same major version

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

Elliotte Rusty Harold updated MENFORCER-360:
--------------------------------------------
    Issue Type: New Feature  (was: Improvement)

> requireUpperBoundDeps should have option to check for same major version
> ------------------------------------------------------------------------
>
>                 Key: MENFORCER-360
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-360
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>    Affects Versions: 3.0.0-M3
>            Reporter: Guy Veraghtert
>            Priority: Trivial
>
> In our project we use semantic versioning for our dependencies ([https://semver.org/|https://semver.org/).])
> The requireUpperBoundDeps rule already checks for compatible versions, but we would like to have the option to specify that no major (i.e. breaking) versions are mixed.
> So a (transitive) dependency on groupId:artifactId:1.0.0 and on groupId:artifactId:2.0.0 means that we have a conflict.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)