[
https://jira.codehaus.org/browse/MNG-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348049#comment-348049
]
Jason van Zyl commented on MNG-5635:
------------------------------------
I think here we can just introspect the class in the IDE which isn't terribly
expensive. What would the plugin.xml look like in your opinion? Can you provide
an example?
> No info generated for nested classes in mojo config
> ---------------------------------------------------
>
> Key: MNG-5635
> URL: https://jira.codehaus.org/browse/MNG-5635
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: IDEs, Plugin API, Plugins and Lifecycle
> Affects Versions: 3.2.1
> Reporter: Axel Fontaine
>
> For more advanced plugins, it is nice to have nested objects in order to
> group settings
> (http://maven.apache.org/guides/plugin/guide-java-plugin-development.html#Other_Object_Classes)
> Currently the metadata for these does not get generated nor included in
> plugin.xml (even though it is present in the original class).
> This in turn leads to IDEs not being able to offer completion, documentation,
> validation, ... for these attributes, hindering reliability and
> discoverability, two of Maven's primary strengths.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
