maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Duell (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MENFORCER-242) rule: "requirePluginVersions" - please don't drop parameter "unCheckedPlugins"
Date Wed, 14 Oct 2015 16:00:06 GMT
Eric Duell created MENFORCER-242:
------------------------------------

             Summary: rule: "requirePluginVersions" - please don't drop parameter "unCheckedPlugins"
                 Key: MENFORCER-242
                 URL: https://issues.apache.org/jira/browse/MENFORCER-242
             Project: Maven Enforcer Plugin
          Issue Type: Wish
          Components: Rule API
    Affects Versions: 1.0
            Reporter: Eric Duell
            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
(v6.3.4#6332)

Mime
View raw message