[jira] [Commented] (MPLUGIN-243) add an option to hide a mojo parameter from generated documentation
[ https://issues.apache.org/jira/browse/MPLUGIN-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252520#comment-17252520 ] Michael Osipov commented on MPLUGIN-243: No problem, just let me know when you want/can make some progress. > 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)
[jira] [Commented] (MPLUGIN-243) add an option to hide a mojo parameter from generated documentation
[ 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)
[jira] [Commented] (MPLUGIN-243) add an option to hide a mojo parameter from generated documentation
[ https://issues.apache.org/jira/browse/MPLUGIN-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248334#comment-17248334 ] Michael Osipov commented on MPLUGIN-243: [~muesli4], do you want me to reopen? No one worked on this for several years. Do you consider to pick this up or do we want this to dangle for another 5 years? > 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)
[jira] [Commented] (MPLUGIN-243) add an option to hide a mojo parameter from generated documentation
[ 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)
