[jira] (MNG-5515) Allow scope validator to be configurable

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MNG-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MNG-5515:
--------------------------------

    Affects Version/s: 3.2.x

> Allow scope validator to be configurable
> ----------------------------------------
>
>                 Key: MNG-5515
>                 URL: https://jira.codehaus.org/browse/MNG-5515
>             Project: Maven
>          Issue Type: Improvement
>          Components: Bootstrap & Build
>    Affects Versions: 3.1.0, 3.2.x
>            Reporter: Scott Hamilton
>            Priority: Minor
>         Attachments: mvn3-DefaultModelValidator-scopeValidator.patch
>
>
> For projects using flex mojos, those flex mojos use non-standard scopes (e.g. internal, external, rsl, cached, etc.).  This throws warnings into the build output, which if one's goal is to keep the build clean, is a problem.
> In the DefaultModelValidator class there is even this comment:
> /*
>  * TODO: Extensions like Flex Mojos use custom scopes like "merged", "internal", "external", etc.
>  * In order to don't break backward-compat with those, only warn but don't error out.
>  */
> This enhancement is to allow a configuration setting to either skip or configure the allowable scopes to preclude these warnings.  Ideally this could be fixed in a better way (perhaps through a project extension plugin) but this was the least intrusive way I saw to get this to work.
> See the attached patch file where I allow two different system/user settings.  "skipScopeValidation" can be set to skip validation of the scopes entirely, or "additionalScopes" can be set to a comma-delimited list of additional scopes that will pass validation.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)