[
https://issues.apache.org/jira/browse/MPLUGIN-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248235#comment-17248235
]
Moritz Bruder commented on MPLUGIN-243:
---------------------------------------
While I agree with [~rfscholte] about wrong design, there is also another use
case where this may come in handy: Imagine you want to hide certain settings
from your users because you have some internal functionality that you don't
want to expose to end-users.
> 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)
