[MNG-1567] improvements to complex mojo configuration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Component/s: Plugins and Lifecycle
• Assignee: Unassigned
• Reporter: Brett Porter
• Created: 14/Nov/05 22:13
• Updated: 27/Jun/20 06:49
• Resolved: 22/Jan/14 20:31

Description

currently, you can specify an object in the configuration that allows nesting multiple levels of config. This is helpful, but it would be good to be able to validate those portions of the configuration as well as set default values, and make them extendable by making them fully fledged configured component requirements.

basically:

• be able to specify expressions and default values within the fields of the object, not just the top mojo, as long as it is in the same source tree as the mojo (like extends)
• to be able to put a polymorphic object in there without an implementation given in the pom. This might require selectors, and so might be best left until a later version (se elinked issue for a use case)

I haven't tried, but it might already be possible to do this (from components.xml), and we just need to wire up the tools to handle it.

Issue Links

• relates to: MCOMPILER-16 ability to separate compilation parameters for different compilers / create a compilation configuration object