[
https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074059#comment-16074059
]
Robert Scholte commented on MENFORCER-276:
------------------------------------------
This one is tricky. The original definition is that every GA can have only 1
version, no matter the scope. This means you can change the version of a
transitive compile-scoped dependency with a direct test-scoped dependency. We
need to analyze the impact if we can improve this in a new major version of
Maven.
So I'm not sure if this request does reflect the preferred behavior.
> Allow ignoring dependency scopes in RequireUpperBoundDeps
> ---------------------------------------------------------
>
> Key: MENFORCER-276
> URL: https://issues.apache.org/jira/browse/MENFORCER-276
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Reporter: Oleg Nenashev
>
> We have recently adopted RequireUpperBoundDeps in the Jenkins project
> (https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it,
> [~jgl...@netbeans.org] added a support of ignoring particular dependencies in
> MENFORCER-273.
> Sometimes we declare dependencies between plugins for testing purposes
> (scope=test), and in such case RequireUpperBoundDeps fails the build if there
> is a test dependency conflicting with the main code. Although it may cause
> instability of tests (including false positive results), it does not really
> impact the distributable package in our case.
> I propose to add another option for filtering of dependency scopes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
