maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Kilding (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MNG-7243) Add Maven Enforcer Plugin rule that bans deprecated dependencies
Date Wed, 08 Sep 2021 15:31:00 GMT

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

Chris Kilding commented on MNG-7243:
------------------------------------

This rule, unlike other Enforcer rules, is non-deterministic: a project that passes it today
will fail it in future if one or more project dependencies become deprecated. That's worth
a discussion as was hinted on the mailing list. This is why I propose the 'skip' property
as an initial solution, to help developers who need to debug a project that contains deprecated
dependencies; it will allow them to turn the rule on and off during their debugging.

> Add Maven Enforcer Plugin rule that bans deprecated dependencies
> ----------------------------------------------------------------
>
>                 Key: MNG-7243
>                 URL: https://issues.apache.org/jira/browse/MNG-7243
>             Project: Maven
>          Issue Type: Sub-task
>            Reporter: Chris Kilding
>            Priority: Minor
>
> Add a rule to the Maven Enforcer Plugin that fails if any project dependencies are deprecated.
> Something like <banDeprecatedDependencies>.
> The rule should also have a 'skip' property that can be passed via the command line (similar
to Surefire's -DskipTests), which allows the user to temporarily bypass it when debugging
a project.



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

Mime
View raw message