[MNG-5515] Allow scope validator to be configurable

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.1.0, 3.2.x
• Component/s: Bootstrap & Build
• Flags: Patch
• Assignee: Unassigned
• Reporter: Scott Hamilton
• Created: 19/Sep/13 09:23
• Updated: 23/Dec/19 02:35

Description

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.