maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Glick (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps
Date Mon, 03 Dec 2018 17:10:00 GMT

    [ https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707542#comment-16707542
] 

Jesse Glick commented on MENFORCER-276:
---------------------------------------

[~matthies] not sure I understand. If you run the rule as currently implemented, it reports
violations in all scopes, and a given dependency can only have one version used in all of
the scopes in which it appears. Is there a concrete example you have in mind of this “hiding”?

> 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
>            Priority: Major
>
> We have recently adopted RequireUpperBoundDeps in the Jenkins project (https://github.com/jenkinsci/plugin-pom/pull/67).
In order to implement it, [~jglick@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
(v7.6.3#76005)

Mime
View raw message