[
https://issues.apache.org/jira/browse/MENFORCER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193790#comment-17193790
]
Robert Scholte commented on MENFORCER-360:
------------------------------------------
In theory there might be breaking changes, but what if your code doesn't touch
that change?
Backwards compatibility is quite important, even when changing the major
version.
It all depends on the kind of project you're working one.
commons-lang did the right thing: as a utility library they introduced a new
artifactId and new package to allow multiple versions next to each other.
spring-framework can also change their version without to much issues, as long
as you ensure to use the same version for all libraries(using a BOM)
I don't think this proposal will make your project more reliable.
Instead I suggest to have a look at
https://github.com/GoogleCloudPlatform/cloud-opensource-java/wiki/Linkage-Checker-Enforcer-Rule
> 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: Improvement
> 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)
