[
https://issues.apache.org/jira/browse/MPLUGIN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839728#comment-15839728
]
Konrad Windszus commented on MPLUGIN-308:
-----------------------------------------
I think this can be closed as invalid, as the nested types do not evaluate any
@Parameter annotations at all
(http://maven.40175.n5.nabble.com/why-the-defaultValue-is-not-being-injected-in-Parameter-inside-a-complex-parameter-bean-td5835732.html).
So the enhancement already tracked in MPLUGIN-9 should actually be enough.
> Improve mojo documentation for "plugin:report" on complex parameter types
> -------------------------------------------------------------------------
>
> Key: MPLUGIN-308
> URL: https://issues.apache.org/jira/browse/MPLUGIN-308
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
> Affects Versions: 3.4
> Reporter: Konrad Windszus
> Assignee: Robert Scholte
>
> In case you have a Mojo with a custom complex parameter, i.e. a Parameter of
> type {{MyParam}}, where {{MyParam}} again has some fields annotated with
> {{@Parameter}}, the documentation of {{MyParam}} with its individual pieces
> should be part of the mojo documentation being generated by {{plugin:report}}.
> See also
> http://stackoverflow.com/questions/20696862/inject-parameter-in-different-class-in-maven-plugin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)