[
https://issues.apache.org/jira/browse/GROOVY-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490425#comment-16490425
]
Paul King commented on GROOVY-8592:
-----------------------------------
There is a three part answer:
(1) docs within the docs zip (includes asciidoc, javadocs, groovydoc) will need
to ready with the release
(2) even though (1) is true, we keep snapshot doco for the next release on the
website, so we can update that and point people to it if we get something badly
wrong
(3) anything on the groovy website we can update continuously, e.g. the
groovy-2.5 release notes.
I have no doubt we'll find numerous errors/bugs when people start using 2.5.0
in more mainstream projects and we'll likely need a 2.5.1 in 3-6 (guess) weeks
anyway.
> Migrate command line tools to picocli version of CliBuilder
> -----------------------------------------------------------
>
> Key: GROOVY-8592
> URL: https://issues.apache.org/jira/browse/GROOVY-8592
> Project: Groovy
> Issue Type: Improvement
> Components: command line processing
> Affects Versions: 2.5.0-rc-3
> Reporter: Remko Popma
> Assignee: Paul King
> Priority: Major
> Fix For: 2.5.0
>
>
> The following command line tools use either {{groovy.cli.commons.CliBuilder}}
> or implicitly use {{groovy.util.CliBuilder}} which delegates to the
> commons-cli version of CliBuilder:
> * groovyConsole (groovy.ui.Console)
> * groovydoc (org.codehaus.groovy.tools.groovydoc.Main)
> * groovysh (org.codehaus.groovy.tools.shell.Main)
> This ticket proposes to use {{groovy.cli.picocli.CliBuilder}} instead, so
> that all command line tools in the {{bin}} directory of the Groovy
> distribution show usage help in ANSI colors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
