[
https://issues.apache.org/jira/browse/MNG-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146804#comment-17146804
]
Abhinay Agarwal commented on MNG-1567:
--------------------------------------
This can be a good addition. Current complex parameters lack a lot of features
and it always feels like a bargain when you want to use it.
I would vote on this issue but its marked as "closed".
> improvements to complex mojo configuration
> ------------------------------------------
>
> Key: MNG-1567
> URL: https://issues.apache.org/jira/browse/MNG-1567
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Brett Porter
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
