maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <>
Subject [jira] [Closed] (MENFORCER-242) rule: "requirePluginVersions" - please don't drop parameter "unCheckedPlugins"
Date Fri, 16 Mar 2018 19:17:00 GMT


Karl Heinz Marbaise closed MENFORCER-242.
    Resolution: Pending Closed

> rule: "requirePluginVersions" - please don't drop parameter "unCheckedPlugins"
> ------------------------------------------------------------------------------
>                 Key: MENFORCER-242
>                 URL:
>             Project: Maven Enforcer Plugin
>          Issue Type: Wish
>          Components: Rule API
>    Affects Versions: 1.0
>            Reporter: Eric Thieme
>            Priority: Minor
> In MENFORCER-62 "unCheckedPluginList " (a comma seperated list) was requested instead
of "unCheckedPlugins" (a real list). 
> As a solution now both parameters are availbale and the "old" one is deprecated. But
why can't we have both parameters? I understand the use case but in my case just a comma seperated
list would not match my project requirements. On the one hand its not really readable to have
more than a few plugins in one line and on the other hand I prefer to have the list of unchecked
plugins tagged in the SCM and not in a settings.xml.
> Can't you remove this coment "NOTE: This is deprecated, use unCheckedPluginList instead."
and support both parameters in coming versions?

This message was sent by Atlassian JIRA

View raw message