[
https://issues.apache.org/jira/browse/MPLUGIN-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248344#comment-17248344
]
Moritz Bruder commented on MPLUGIN-243:
---------------------------------------
[~michael-o], I'm currently reading into the code. I'm interested in working on
a few issues regarding the Parameter-Annotation. This also includes to make
the programmatic mechanism for complex types as parameters a bit safer (e.g.,
by providing a different annotation). First of all, I want to know whether
someone is interested in such changes or if there is opposition to those ideas.
It may take some time because I don't have that much.
> add an option to hide a mojo parameter from generated documentation
> -------------------------------------------------------------------
>
> Key: MPLUGIN-243
> URL: https://issues.apache.org/jira/browse/MPLUGIN-243
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: maven-plugin-annotations,
> maven-plugin-tools-annotations, maven-plugin-tools-java,
> maven-plugin-tools-javadoc
> Affects Versions: 3.2
> Reporter: Herve Boutemy
> Priority: Minor
>
> when a parameter is defined in a parent mojo, because it needs to be shared
> by some child mojos, but some other child mojos don't use the feature,
> parameter documentation just adds unnecessary complexity
> see MDEP-413 for such an example
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
