[
https://issues.apache.org/jira/browse/GROOVY-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450309#comment-16450309
]
Remko Popma commented on GROOVY-8521:
-------------------------------------
I tried a few things but I am unable to get GroovyDocs generated for any of the
subprojects (including {{groovy-cli-commons}} and {{groovy-cli-picocli}}).
> Create new groovy-cli-commons module
> ------------------------------------
>
> Key: GROOVY-8521
> URL: https://issues.apache.org/jira/browse/GROOVY-8521
> Project: Groovy
> Issue Type: Improvement
> Components: command line processing
> Reporter: Remko Popma
> Assignee: Paul King
> Priority: Major
>
> GROOVY-8520 proposes a new implementation of CliBuilder based on a different
> command line parser.
> Until now, CliBuilder exposes some properties that allow client code direct
> access to the underlying commons-cli parser and usage help formatter. The new
> CliBuilder implementation will not provide these {{commons-cli}}-based
> properties any more (although it may expose picocli equivalents).
> This ticket is to create a separate module (groovy-cli-commons or similar)
> with the existing CliBuilder implementation (but with probably a package name
> change) that won't be referenced in the groovy-all pom. Client code that
> relies on those bits of the functionality, can use the legacy version.
> Ultimately commons-cli should be referenced only in this new module. See also
> [mailing list
> discussion|https://lists.apache.org/thread.html/cf79e403113a3b57511f0efd43065d9f07f24b38557d9b280e42905f@%3Cdev.groovy.apache.org%3E].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
