I've started to make this change.
Note that there is some impact when upgrading:
Script authors need to use
`@Grab('info.picocli:*picocli-groovy*:4.x')` from version 4.0, since
`@Grab('info.picocli:picocli:4.x')` will not work.
On Sat, Jun 1, 2019 at 1:28 AM MG wrote:
> Hi Remko,
>
> I agree
Thursday, May 30, 2019 3:05 PM
> *To:* us...@groovy.apache.org
> *Cc:* dev@groovy.apache.org
> *Subject:* Re: requesting your advice on picocli modules
>
> + 1 picoli-groovy.jar
>
> Great project BTW!
>
> El jue., 30 may. 2019 a las 14:51, Remko Popma ()
> escribi
Could your "picocli.groovy" package move to the groovy-cli-picocli subproject?
From: Mario Garcia
Sent: Thursday, May 30, 2019 3:05 PM
To: us...@groovy.apache.org
Cc: dev@groovy.apache.org
Subject: Re: requesting your advice on picocli modules
+ 1 picoli-groovy.jar
Great project BTW!
El jue., 30 may. 2019 a las 14:51, Remko Popma ()
escribió:
> Hi,
>
> I maintain the picocli library for creating command line applications in
> Groovy, Java, and other JVM languages.
> I have a question for the Groovy community (both users and
Hi,
I maintain the picocli library for creating command line applications in
Groovy, Java, and other JVM languages.
I have a question for the Groovy community (both users and developers):
Currently, the picocli main jar contains both the core `picocli` package
and a `picocli.groovy` package with
