Re: Groovy 4.0.0: No such property: importPackages for class: org.codehaus.groovy.ast.ModuleNode

[Remko Popma]

I checked picocli.
picocli-groovy has an AST transformation (PicocliScriptASTTransformation)
but the source code of that class also does not contain the word
"importPackages".
So that is not it either.

On Fri, Mar 4, 2022 at 10:28 PM Dirk Heinrichs 
wrote:

> Am Freitag, dem 04.03.2022 um 23:12 +1000 schrieb Paul King:
>
> I'd rename "groovy-astbuilder-4.0.0.jar" in your "lib" folder to something
> like "groovy-astbuilder-4.0.0.jar.bak" and see if that makes any
> difference. Just a total guess but that's the only place in the Groovy
> codebase I could find using the "importPackages" name.
>
>
> No, doesn't make any difference. Error message is exactly the same.
>
> Bye...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>

Re: GraalVM native image for Groovy apps

[Remko Popma]

Wow, very extensive. Impressive!
How would you like feedback?
As GitHub issues/pull requests, on this mailing list, or some other way?

Remko

On Sun, Jan 31, 2021 at 2:28 Damir Murat  wrote:

> Hi,
>
> I'm writing an article exploring the options for creating GraalVM native
> images for
> Groovy/Micronaut/picocli CLI applications. Although the article is content
> complete,
> I'm still considering it as a draft, and I'm looking for feedback.
>
> If somebody is interested, the article is here:
>
> https://github.com/croz-ltd/klokwrk-project/blob/master/support/documentation/article/groovy-graalvm-native-image/groovy-graalvm-native-image.md
>
> Tnx,
> Damir Murat
>

Re: Congratulations to our newest committer Mikko Värri

[Remko Popma]

Congratulations Mikko!

On Mon, Jun 8, 2020 at 9:06 AM 孙 岚  wrote:

> Congratulations to Mikko Värri who is now an Apache Groovy committer:
>
> https://projects.apache.org/committee.html?groovy
> http://people.apache.org/phonebook.html?unix=groovy
>
> Mikko has been mostly working on the groovydoc, which is important to
> Groovy users and developers.
>
> Keep on your great work, Mikko.
>
> Cheers,
> Daniel Sun
>
>

Re: [ANNOUNCE] Apache Groovy 2.5.11 released

[Remko Popma]

Thanks Paul!

Remko.



> On Apr 10, 2020, at 19:06, Paul King  wrote:
> 
> Dear community,
> 
> The Apache Groovy team is pleased to announce version 2.5.11 of Apache Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the https://groovy.apache.org website.
> 
> This release is a maintenance release of the GROOVY_2_5_X branch.
> It is strongly encouraged that all users using prior
> versions on this branch upgrade to this version.
> 
> This release includes 6 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12347744
> 
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: https://groovy.apache.org/download.html
> We recommend you verify your installation using the information on that page.
> 
> Jars are also available within the major binary repositories.
> 
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
> 
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
> 
> Best regards,
> 
> The Apache Groovy team.

Re: [ANNOUNCE] Apache Groovy 2.5.9 released

[Remko Popma]

Thank you, Paul!



> On Jan 14, 2020, at 17:33, Daniel.Sun  wrote:
> 
> Nice work, Paul :-)
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> -
> Apache Groovy committer & PMC member 
> Blog: http://blog.sunlan.me 
> Twitter: @daniel_sun 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: [ANNOUNCE] Apache Groovy 2.4.18 released

[Remko Popma]

Thank you, Paul!


> On Jan 14, 2020, at 17:34, Daniel.Sun  wrote:
> 
> Nice work, Paul :-)
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> -
> Apache Groovy committer & PMC member 
> Blog: http://blog.sunlan.me 
> Twitter: @daniel_sun 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: [ANNOUNCE] Apache Groovy 3.0.0-beta-2 Released

[Remko Popma]

The permalink is auto-generated by the wonderful (not) Apache
Roller blogging software.

I agree it's very annoying.
I recommend using a URL shortener link like http://tiny.cc/akhr9y when
publishing on social media.

On Mon, Jul 15, 2019 at 7:55 PM Guillaume Laforge 
wrote:

> The link URL contains beta-ONE instead of TWO :-)
>
> On Mon, Jul 15, 2019 at 12:33 PM Remko Popma 
> wrote:
>
>> Blogged:
>> https://blogs.apache.org/groovy/entry/groovy-3-0-0-beta1
>>
>> On Mon, Jul 15, 2019 at 1:22 AM Guillaume Laforge 
>> wrote:
>>
>>> Congrats on this release!
>>>
>>> Le dim. 14 juil. 2019 à 12:57, 孙 岚  a écrit :
>>>
>>>> Dear community,
>>>>
>>>> The Apache Groovy team is pleased to announce version 3.0.0-beta-2 of
>>>> Apache Groovy.
>>>> Apache Groovy is a multi-faceted programming language for the JVM.
>>>> Further details can be found at the https://groovy.apache.org website.
>>>>
>>>> This is a pre-release of a new version of Groovy.
>>>> We greatly appreciate any feedback you can give us when using this
>>>> version.
>>>>
>>>> This release includes 40 bug fixes/improvements as outlined in the
>>>> changelog:
>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12345498
>>>>
>>>> Sources, convenience binaries, downloadable documentation and an SDK
>>>> bundle can be found at: https://groovy.apache.org/download.html
>>>> We recommend you verify your installation using the information on that
>>>> page.
>>>>
>>>> Jars are also available within the major binary repositories.
>>>>
>>>> We welcome your help and feedback and in particular want
>>>> to thank everyone who contributed to this release.
>>>>
>>>> For more information on how to report problems, and to get involved,
>>>> visit the project website at https://groovy.apache.org/
>>>>
>>>> *Note: Apache Groovy 3.0.0-beta-2 was compiled with JDK8, so the
>>>> illegal access warnings will come back if you use JDK9+. But don't worry,
>>>> we will do another release in a week or two. Please verify the issues you
>>>> reported first and give us feedback, which will help us improve the quality
>>>> of next release.*
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> The Apache Groovy team.
>>>>
>>>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge <http://twitter.com/glaforge>
>

Re: [ANNOUNCE] Apache Groovy 3.0.0-beta-2 Released

[Remko Popma]

Blogged:
https://blogs.apache.org/groovy/entry/groovy-3-0-0-beta1

On Mon, Jul 15, 2019 at 1:22 AM Guillaume Laforge 
wrote:

> Congrats on this release!
>
> Le dim. 14 juil. 2019 à 12:57, 孙 岚  a écrit :
>
>> Dear community,
>>
>> The Apache Groovy team is pleased to announce version 3.0.0-beta-2 of
>> Apache Groovy.
>> Apache Groovy is a multi-faceted programming language for the JVM.
>> Further details can be found at the https://groovy.apache.org website.
>>
>> This is a pre-release of a new version of Groovy.
>> We greatly appreciate any feedback you can give us when using this
>> version.
>>
>> This release includes 40 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12345498
>>
>> Sources, convenience binaries, downloadable documentation and an SDK
>> bundle can be found at: https://groovy.apache.org/download.html
>> We recommend you verify your installation using the information on that
>> page.
>>
>> Jars are also available within the major binary repositories.
>>
>> We welcome your help and feedback and in particular want
>> to thank everyone who contributed to this release.
>>
>> For more information on how to report problems, and to get involved,
>> visit the project website at https://groovy.apache.org/
>>
>> *Note: Apache Groovy 3.0.0-beta-2 was compiled with JDK8, so the illegal
>> access warnings will come back if you use JDK9+. But don't worry, we
>> will do another release in a week or two. Please verify the issues you
>> reported first and give us feedback, which will help us improve the quality
>> of next release.*
>>
>>
>> Best regards,
>>
>> The Apache Groovy team.
>>
>

Re: [ANNOUNCE] Groovy 3.0.0-beta-2 Windows Installer Released

[Remko Popma]

Blogged:
https://blogs.apache.org/groovy/entry/groovy-3-0-0-beta2

On Mon, Jul 15, 2019 at 2:23 AM Guillaume Laforge 
wrote:

> That was fast 
>
> Le dim. 14 juil. 2019 à 19:13, Daniel.Sun  a écrit :
>
>> Nice work, Keegan :-)
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>> -
>> Apache Groovy committer & PMC member
>> Blog: http://blog.sunlan.me
>> Twitter: @daniel_sun
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>>
>

Re: Problem running find execute has error

[Remko Popma]

Maybe in Groovy you don’t need to escape the semicolon. 
The semicolon has special meaning in the shell so there it does need to be 
escaped, but in the Groovy command you can just pass it as the delimiter arg to 
-exec. 

Remko.

(Shameless plug) Every java main() method deserves http://picocli.info

> On Jun 12, 2019, at 3:05, Sverre Moe  wrote:
> 
> Groovy is doing something strange with my execute command.
> Or perhaps something wrong with my code I cannot see.
> 
> vim find.groovy
> def sout = new StringBuilder(), serr = new StringBuilder()  
> def proc = "find RPMS -regex '.*/package-name-[0-9.]+-.\\.x86_64\\.rpm' -exec 
> cp -v {} . \\;".execute()
> proc.consumeProcessOutput(sout, serr)  
> proc.waitForOrKill(1000)  
> println "out> $sout"  
> println "err> $serr"
> 
> Create the directory and files for testing the find.groovy
> mkdir RPMS
> touch RPMS/package-name-1.0.0-1.x86_64.rpm
> touch RPMS/package-name-devel-1.0.0-1.noarch.rpm
> 
> The output from running the find.groovy seems to suggest the find command is 
> wrong.
> groovy find.groovy
> err> find: argument for «-exec» is missing
> 
> But running it in bash works just fine:
> find RPMS -regex '.*/package-name-[0-9.]+-.\.x86_64\.rpm' -exec cp -v {} . \;
> 'RPMS/package-name-1.0.0-1.x86_64.rpm' -> './package-name-1.0.0-1.x86_64.rpm'
> 
> I can reproduce the error in Bash with an additional slash at the end.
> find RPMS -regex '.*/package-name-[0-9.]+-.\.x86_64\.rpm' -exec cp -v {} . \\;
> find: argument for «-exec» is missing
> 
> 
> /Sverre

Re: requesting your advice on picocli modules

[Remko Popma]

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 option 1) is the cleanest, as well as it being the direction all
> of Groovy seems to be moving.
>
> Cheers,
> mg
>
>
> On 30/05/2019 14:50, Remko Popma wrote:
>
> 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 classes that make it easy for Groovy
> scripts to use picocli annotations. I'm considering splitting up this jar.
>
> In an upcoming major release of the library I plan to provide a Java 9
> JPMS modular jar containing just the core `picocli` package and
> additionally a `module-info.class` to make this jar a full-fledged Java
> module.
>
> The question is what to do with the picocli.groovy package. I see two
> options:
> 1) have a `picocli-groovy` jar containing _only_ the picocli.groovy
> package - this jar would require (have a dependency on) the core picocli
> jar (the JPMS modular jar). Ideally this `picocli-groovy` jar would also be
> a JPMS module, but not sure if that's possible.
> 2) have a `picocli-legacy?` (name TBD) jar containing both the core
> picocli package and the picocli.groovy package - similar to the current
> picocli-3.9.x jar
>
> I believe the first option may be cleanest. Scripts would need to change
> their grape module from @Grab('info.picocli:picocli:$version') to
> @Grab('info.picocli:picocli-groovy:4.0.0') and that would bring in the
> transitive dependency on 'info.picocli:picocli:4.0.0', if my understanding
> is correct.
>
> Can anyone see any drawbacks with this approach?
> Would there be any point in additionally providing a `picocli-legacy`
> (name TBD) jar containing both the core picocli package and the
> picocli.groovy package, similar to the current picocli-3.9.x jar?
>
> On a side-note, has anyone had any issues with putting the
> `module-info.class` in the root of the modular jar versus putting it in
> META-INF/versions/9/ in the jar?
> Some people <https://github.com/moditect/moditect/issues/67> use
> META-INF/versions/9/ as a way to (hopefully) avoid issues with older tools
> unable to cope with the `module-info.class`. Does anyone have any
> experience with this?
>
> Remko
>
>
>

Re: requesting your advice on picocli modules

[Remko Popma]

On Fri, May 31, 2019 at 6:11 AM Milles, Eric (TR Tech, Content & Ops) <
eric.mil...@thomsonreuters.com> wrote:

> Could your "picocli.groovy" package move to the groovy-cli-picocli
> subproject?
>
They do different things: groovy-cli has its own annotations
(@Option, @OptionField, @UnparsedField, etc), to be used with CliBuilder.
The groovy-cli-picocli subproject provides a CliBuilder implementation that
supports these annotations and other Groovy 2.5 CliBuilder features, using
picocli as the underlying parser.

The picocli.groovy package in picocli allows the use of _picocli_
annotations (not groovy-cli annotations) in Groovy scripts. It is not
related to CliBuilder and works with older versions of Groovy.

So, it's probably better to keep them separate to avoid confusion.



>
> --
> *From:* Mario Garcia 
> *Sent:* Thursday, May 30, 2019 3:05 PM
> *To:* users@groovy.apache.org
> *Cc:* d...@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 developers):
>
> Currently, the picocli main jar contains both the core `picocli` package
> and a `picocli.groovy` package with classes that make it easy for Groovy
> scripts to use picocli annotations. I'm considering splitting up this jar.
>
> In an upcoming major release of the library I plan to provide a Java 9
> JPMS modular jar containing just the core `picocli` package and
> additionally a `module-info.class` to make this jar a full-fledged Java
> module.
>
> The question is what to do with the picocli.groovy package. I see two
> options:
> 1) have a `picocli-groovy` jar containing _only_ the picocli.groovy
> package - this jar would require (have a dependency on) the core picocli
> jar (the JPMS modular jar). Ideally this `picocli-groovy` jar would also be
> a JPMS module, but not sure if that's possible.
> 2) have a `picocli-legacy?` (name TBD) jar containing both the core
> picocli package and the picocli.groovy package - similar to the current
> picocli-3.9.x jar
>
> I believe the first option may be cleanest. Scripts would need to change
> their grape module from @Grab('info.picocli:picocli:$version') to
> @Grab('info.picocli:picocli-groovy:4.0.0') and that would bring in the
> transitive dependency on 'info.picocli:picocli:4.0.0', if my understanding
> is correct.
>
> Can anyone see any drawbacks with this approach?
> Would there be any point in additionally providing a `picocli-legacy`
> (name TBD) jar containing both the core picocli package and the
> picocli.groovy package, similar to the current picocli-3.9.x jar?
>
> On a side-note, has anyone had any issues with putting the
> `module-info.class` in the root of the modular jar versus putting it in
> META-INF/versions/9/ in the jar?
> Some people
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_moditect_moditect_issues_67=DwMFaQ=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY=tPJuIuL_GkTEazjQW7vvl7mNWVGXn3yJD5LGBHYYHww=cocTYR8h3W8Rgqstyq52P9cQq-9lpVTUcc3nlMo8bI4=rZMbQ03MlXNGQEPuzueT5_EYYUeSQF8iF1JOgKJpqSw=>
> use META-INF/versions/9/ as a way to (hopefully) avoid issues with older
> tools unable to cope with the `module-info.class`. Does anyone have any
> experience with this?
>
> Remko
>
>

requesting your advice on picocli modules

[Remko Popma]

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 classes that make it easy for Groovy
scripts to use picocli annotations. I'm considering splitting up this jar.

In an upcoming major release of the library I plan to provide a Java 9 JPMS
modular jar containing just the core `picocli` package and additionally a
`module-info.class` to make this jar a full-fledged Java module.

The question is what to do with the picocli.groovy package. I see two
options:
1) have a `picocli-groovy` jar containing _only_ the picocli.groovy package
- this jar would require (have a dependency on) the core picocli jar (the
JPMS modular jar). Ideally this `picocli-groovy` jar would also be a JPMS
module, but not sure if that's possible.
2) have a `picocli-legacy?` (name TBD) jar containing both the core picocli
package and the picocli.groovy package - similar to the current
picocli-3.9.x jar

I believe the first option may be cleanest. Scripts would need to change
their grape module from @Grab('info.picocli:picocli:$version') to
@Grab('info.picocli:picocli-groovy:4.0.0') and that would bring in the
transitive dependency on 'info.picocli:picocli:4.0.0', if my understanding
is correct.

Can anyone see any drawbacks with this approach?
Would there be any point in additionally providing a `picocli-legacy` (name
TBD) jar containing both the core picocli package and the picocli.groovy
package, similar to the current picocli-3.9.x jar?

On a side-note, has anyone had any issues with putting the
`module-info.class` in the root of the modular jar versus putting it in
META-INF/versions/9/ in the jar?
Some people  use
META-INF/versions/9/ as a way to (hopefully) avoid issues with older tools
unable to cope with the `module-info.class`. Does anyone have any
experience with this?

Remko

Re: new GroovyCliBuilder

[Remko Popma]

The new CliBuilder annotations API works well for both the Commons CLI and
the picocli implementation.
(And I agree that the annotations API has some advantages over the previous
DSL style, but that may be a matter of taste.)

Note that you can swap the implementation from Commons CLI to picocli by
changing the import
from

import groovy.cli.commons.CliBuilder

to

import groovy.cli.picocli.CliBuilder

With the latter the usage help will show ANSI colors and gives some other
features like the `cliBuilder.usageMessage
`
property to customize the usage help message.

Glad you like it! :-)


On Sat, May 25, 2019 at 2:11 AM MG  wrote:

> Hi guys,
>
> just wanted to say that I recently had to revisit some older Groovy script 
> code in my project, and I took the opportunity to switch the old CliBuilder 
> implementation to the new Picocli based one 
> (http://docs.groovy-lang.org/latest/html/gapi/groovy/cli/commons/CliBuilder.html
> ) - and I can just say that it is an absolute joy to work with: Concise, 
> elegant, and type safe G-)
>
>
> import groovy.cli.commons.CliBuilder
> import groovy.cli.Option
> import groovy.cli.Unparsed
>
> // Alternative is to use an interface and let Groovy instantiate a class 
> instance from it
> class MyOptions {
>  boolean isTestRun
>  @Option(shortName='h', description='output help info') Boolean help
>  @Option(shortName='r', description='process regular entries') Boolean regular
>  // etc (for supported types outside of Boolean see URL above)
>  @Unparsed List remaining // all additional options given
>
>  MyScriptOptions(boolean isTestRun) { this.isTestRun = isTestRun }
> }
>
>
> final cli = new CliBuilder(usage:'my_powerful_groovy_script')
> def opts = new MyOptions(true)
> cli.parseFromInstance(opts, args.split())  // From now on all cmd line
> params can be accessed in a type safe manner
>
> if(opts.help) {
>   println cli.usage()
>   System.exit(0)
> }
>
> if(opts.regular) {
>   ...
> }
>
> Cheers,
> mg
>
>
>
>
>
>

Re: [ANNOUNCE] Groovy 2.5.7 and 3.0.0-beta-1 Windows Installers Released

[Remko Popma]

Blogged:  https://blogs.apache.org/groovy/entry/groovy-2-5-7-and

On Sat, May 11, 2019 at 11:49 PM Daniel.Sun  wrote:

> Nice work, Keegan!
>
> Cheers,
> Daniel.Sun
>
>
>
>
> -
> Apache Groovy committer & PMC member
> Blog: http://blog.sunlan.me
> Twitter: @daniel_sun
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>

Re: Grape resolve broke in 2.5.6 ?

[Remko Popma]

Fixed in the master and GROOVY_2_5_X branches.
Please verify.

On Thu, Feb 28, 2019 at 6:25 PM Remko Popma  wrote:

> I raised https://issues.apache.org/jira/browse/GROOVY-9012 for this issue.
>
> On Thu, Feb 28, 2019 at 5:38 PM Remko Popma  wrote:
>
>> That’s a bug. Thanks for reporting this.
>>
>> I’ll try to fix this today or tomorrow.
>>
>> Remko.
>>
>> On Feb 28, 2019, at 13:52, Nelson, Erick 
>> wrote:
>>
>> Am I calling it wrong?
>>
>>
>>
>> $ groovy -v
>>
>> Groovy Version: 2.5.6 JVM: 1.8.0_77 Vendor: Oracle Corporation OS: Mac OS
>> X
>>
>>
>>
>> $ grape list | grep jcraft
>>
>> com.jcraft jsch  [0.1.42, 0.1.54, 0.1.55, 0.1.46, 0.1.53]
>>
>>
>>
>> $ grape resolve com.jcraft jsch 0.1.53
>>
>> java.lang.reflect.InvocationTargetException
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> at
>> org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:110)
>>
>> at
>> org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128)
>>
>> Caused by: groovyjarjarpicocli.CommandLine$ExecutionException: Error
>> while running command (org.codehaus.groovy.tools.GrapeMain$Resolve@609e8838):
>> groovy.lang.MissingPropertyException: *No such property: arg for class:
>> org.codehaus.groovy.tools.GrapeMain*
>>
>> at
>> groovyjarjarpicocli.CommandLine.execute(CommandLine.java:1168)
>>
>> at
>> groovyjarjarpicocli.CommandLine.access$800(CommandLine.java:141)
>>
>> at
>> groovyjarjarpicocli.CommandLine$RunLast.handle(CommandLine.java:1367)
>>
>> at
>> groovyjarjarpicocli.CommandLine$RunLast.handle(CommandLine.java:1335)
>>
>> at
>> groovyjarjarpicocli.CommandLine$AbstractParseResultHandler.handleParseResult(CommandLine.java:1243)
>>
>> at
>> groovyjarjarpicocli.CommandLine.parseWithHandlers(CommandLine.java:1526)
>>
>> at
>> groovyjarjarpicocli.CommandLine.parseWithHandler(CommandLine.java:1465)
>>
>> at
>> groovyjarjarpicocli.CommandLine$parseWithHandler$0.call(Unknown Source)
>>
>> at
>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
>>
>> at
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
>>
>> at
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:135)
>>
>> at
>> org.codehaus.groovy.tools.GrapeMain.main(GrapeMain.groovy:72)
>>
>> ... 6 more
>>
>> Caused by: groovy.lang.MissingPropertyException: No such property: arg
>> for class: org.codehaus.groovy.tools.GrapeMain
>>
>> at
>> groovy.lang.MetaClassImpl.invokeStaticMissingProperty(MetaClassImpl.java:1021)
>>
>> at
>> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:1866)
>>
>> at
>> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:1842)
>>
>> at
>> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:3797)
>>
>> at
>> org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:193)
>>
>> at
>> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:468)
>>
>> at
>> org.codehaus.groovy.tools.GrapeMain$Resolve.propertyMissing(GrapeMain.groovy)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> at
>> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:101)
>>
>>

Re: Grape resolve broke in 2.5.6 ?

[Remko Popma]

I raised https://issues.apache.org/jira/browse/GROOVY-9012 for this issue.

On Thu, Feb 28, 2019 at 5:38 PM Remko Popma  wrote:

> That’s a bug. Thanks for reporting this.
>
> I’ll try to fix this today or tomorrow.
>
> Remko.
>
> On Feb 28, 2019, at 13:52, Nelson, Erick 
> wrote:
>
> Am I calling it wrong?
>
>
>
> $ groovy -v
>
> Groovy Version: 2.5.6 JVM: 1.8.0_77 Vendor: Oracle Corporation OS: Mac OS X
>
>
>
> $ grape list | grep jcraft
>
> com.jcraft jsch  [0.1.42, 0.1.54, 0.1.55, 0.1.46, 0.1.53]
>
>
>
> $ grape resolve com.jcraft jsch 0.1.53
>
> java.lang.reflect.InvocationTargetException
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at
> org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:110)
>
> at
> org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128)
>
> Caused by: groovyjarjarpicocli.CommandLine$ExecutionException: Error while
> running command (org.codehaus.groovy.tools.GrapeMain$Resolve@609e8838):
> groovy.lang.MissingPropertyException: *No such property: arg for class:
> org.codehaus.groovy.tools.GrapeMain*
>
> at
> groovyjarjarpicocli.CommandLine.execute(CommandLine.java:1168)
>
> at
> groovyjarjarpicocli.CommandLine.access$800(CommandLine.java:141)
>
> at
> groovyjarjarpicocli.CommandLine$RunLast.handle(CommandLine.java:1367)
>
> at
> groovyjarjarpicocli.CommandLine$RunLast.handle(CommandLine.java:1335)
>
> at
> groovyjarjarpicocli.CommandLine$AbstractParseResultHandler.handleParseResult(CommandLine.java:1243)
>
> at
> groovyjarjarpicocli.CommandLine.parseWithHandlers(CommandLine.java:1526)
>
> at
> groovyjarjarpicocli.CommandLine.parseWithHandler(CommandLine.java:1465)
>
> at
> groovyjarjarpicocli.CommandLine$parseWithHandler$0.call(Unknown Source)
>
> at
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
>
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
>
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:135)
>
> at
> org.codehaus.groovy.tools.GrapeMain.main(GrapeMain.groovy:72)
>
> ... 6 more
>
> Caused by: groovy.lang.MissingPropertyException: No such property: arg for
> class: org.codehaus.groovy.tools.GrapeMain
>
> at
> groovy.lang.MetaClassImpl.invokeStaticMissingProperty(MetaClassImpl.java:1021)
>
> at
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:1866)
>
> at
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:1842)
>
> at
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:3797)
>
> at
> org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:193)
>
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:468)
>
> at
> org.codehaus.groovy.tools.GrapeMain$Resolve.propertyMissing(GrapeMain.groovy)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:101)
>
> at
> groovy.lang.MetaClassImpl.invokeMissingProperty(MetaClassImpl.java:889)
>
> at
> groovy.lang.MetaClassImpl$12.getProperty(MetaClassImpl.java:2016)
>
> at
> org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.getProperty(GetEffectivePogoPropertySite.java:85)
>
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:309)
>
> at
> org.codehaus.groovy.tools.GrapeMain$Resolve.run(GrapeMain.groovy:235)
>
> at
> groovyjarjarpicocli.

Re: Grape resolve broke in 2.5.6 ?

[Remko Popma]

That’s a bug. Thanks for reporting this. 

I’ll try to fix this today or tomorrow. 

Remko.

> On Feb 28, 2019, at 13:52, Nelson, Erick  wrote:
> 
> Am I calling it wrong?
>  
> $ groovy -v
> Groovy Version: 2.5.6 JVM: 1.8.0_77 Vendor: Oracle Corporation OS: Mac OS X
>  
> $ grape list | grep jcraft
> com.jcraft jsch  [0.1.42, 0.1.54, 0.1.55, 0.1.46, 0.1.53]
>  
> $ grape resolve com.jcraft jsch 0.1.53
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:110)
> at 
> org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128)
> Caused by: groovyjarjarpicocli.CommandLine$ExecutionException: Error while 
> running command (org.codehaus.groovy.tools.GrapeMain$Resolve@609e8838): 
> groovy.lang.MissingPropertyException: No such property: arg for class: 
> org.codehaus.groovy.tools.GrapeMain
> at 
> groovyjarjarpicocli.CommandLine.execute(CommandLine.java:1168)
> at 
> groovyjarjarpicocli.CommandLine.access$800(CommandLine.java:141)
> at 
> groovyjarjarpicocli.CommandLine$RunLast.handle(CommandLine.java:1367)
> at 
> groovyjarjarpicocli.CommandLine$RunLast.handle(CommandLine.java:1335)
> at 
> groovyjarjarpicocli.CommandLine$AbstractParseResultHandler.handleParseResult(CommandLine.java:1243)
> at 
> groovyjarjarpicocli.CommandLine.parseWithHandlers(CommandLine.java:1526)
> at 
> groovyjarjarpicocli.CommandLine.parseWithHandler(CommandLine.java:1465)
> at 
> groovyjarjarpicocli.CommandLine$parseWithHandler$0.call(Unknown Source)
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:135)
> at 
> org.codehaus.groovy.tools.GrapeMain.main(GrapeMain.groovy:72)
> ... 6 more
> Caused by: groovy.lang.MissingPropertyException: No such property: arg for 
> class: org.codehaus.groovy.tools.GrapeMain
> at 
> groovy.lang.MetaClassImpl.invokeStaticMissingProperty(MetaClassImpl.java:1021)
> at 
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:1866)
> at 
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:1842)
> at 
> groovy.lang.MetaClassImpl.getProperty(MetaClassImpl.java:3797)
> at 
> org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:193)
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:468)
> at 
> org.codehaus.groovy.tools.GrapeMain$Resolve.propertyMissing(GrapeMain.groovy)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:101)
> at 
> groovy.lang.MetaClassImpl.invokeMissingProperty(MetaClassImpl.java:889)
> at 
> groovy.lang.MetaClassImpl$12.getProperty(MetaClassImpl.java:2016)
> at 
> org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.getProperty(GetEffectivePogoPropertySite.java:85)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:309)
> at 
> org.codehaus.groovy.tools.GrapeMain$Resolve.run(GrapeMain.groovy:235)
> at 
> groovyjarjarpicocli.CommandLine.execute(CommandLine.java:1160)
> ... 17 more
>  
> $ grape help resolve
> Enumerates the jars used by a grape
> Usage: grape resolve [-adhisv] (  )+
>  
> Prints the file locations of the jars representing the artifcats for the
> specified module(s) and the respective transitive dependencies.
>  
> Parameters:
>Which module group the module comes from. Translates 
> directly
> to a Maven groupId or an Ivy Organization. Any group
> matching /groovy[x][\..*]^/ is reserved and may have
> special meaning to the groovy endorsed modules.

Re: [ANNOUNCE] Groovy 3.0.0-alpha-4 Windows Installer Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-3-0-0-alpha1

Please share on social media.

On Mon, Dec 31, 2018 at 11:57 AM Keegan Witt  wrote:

> I didn't see any groovy-3.0 snapshots in the snapshot repo:
> https://oss.sonatype.org/content/repositories/snapshots/org/spockframework/spock-core/.
> Did they move them somewhere else?  Or they just haven't pushed any
> snapshots yet?
>
> On Sun, Dec 30, 2018 at 9:31 PM Paul King  wrote:
>
>> Thanks Keegan!
>>
>> For anyone interested, you should be able to use snapshot versions of
>> Spock with Groovy 3.0.0.
>>
>>
>> On Mon, Dec 31, 2018 at 11:39 AM Keegan Witt 
>> wrote:
>>
>>> The Windows installer for Groovy 3.0.0-alpha-4 is available from the
>>> usual place:
>>> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-alpha-4-installer.exe
>>> .
>>>
>>> Note this installer doesn't include Spock since there isn't a Spock
>>> release compatible with Groovy 3.0.
>>>
>>> -Keegan
>>>
>>

Re: [ANNOUNCE] Groovy 2.5.5 Windows Installer Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-5-windows

Please share on social media.

On Tue, Dec 25, 2018 at 2:24 AM Keegan Witt  wrote:

> The Windows installer for Groovy 2.5.5 is available from the usual place:
> https://bintray.com/groovy/Distributions/Windows-Installer/groovy-2.5.5-installer
> .
>
> -Keegan
>

Re: [ANNOUNCE] Apache Groovy 2.5.5 released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-5-released

Please share on social media.

On Mon, Dec 24, 2018 at 5:09 PM Guillaume Laforge 
wrote:

> Congrats everyone!
>
> On Mon, Dec 24, 2018 at 5:14 AM Daniel.Sun  wrote:
>
>> Nice work, Paul.
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>>
>> -
>> Apache Groovy committer
>> Blog: http://blog.sunlan.me
>> Twitter: @daniel_sun
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC Vice-President
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: What is the best replacement for running scripts using groovy-all?

[Remko Popma]

You may be interested in the Gradle application plugin. This creates a 
distribution zip file with all the dependencies and some starter scripts. 
https://docs.gradle.org/current/userguide/application_plugin.html

The only customization would be to add your custom script to the bin/ directory 
where the starter scripts live. 


Remko.
(Shameless plug) Every java main() method deserves http://picocli.info

> On Dec 20, 2018, at 8:00, Paul Moore  wrote:
> 
>> On Wed, 19 Dec 2018 at 22:46, MG  wrote:
>> 
>> Hi,
>> 
>> out of curiosity (and because having a fat jar again might be
>> conventient at some point in the future in my work environment (also no
>> internet access)):
>> 
>> This solution proposed by Keith does not work
>> https://github.com/gradle/gradle-groovy-all
>> ?
> 
> See https://github.com/gradle/gradle-groovy-all/issues/1
> 
> Basically, yes it does, but only for groovy.ui.GroovyMain (which is
> fine) and they don't support usage for anything other than Gradle's
> purposes and they are looking to discontinue it once Gradle no longer
> needs it (which isn't quite as fine ;-))
> 
> In addition, by not going with that solution, I've learned a lot about
> Gradle and how to use it to solve my problem, which is much better, as
> not only do I have a solution, I also learned something new :-) By the
> way - my Gradle solution also doesn't work for groovy.ui.Console, but
> that's fine as I say above (and it's a chance to learn more, working
> out why :-))
> 
> Paul

Re: [ANNOUNCE] Groovy 2.4.16 Windows Installer Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-4-16-windows

On Mon, Dec 17, 2018 at 2:51 AM Keegan Witt  wrote:

> The Windows installer for Groovy 2.4.16 is available from the usual
> place:
> https://bintray.com/groovy/Distributions/Windows-Installer/groovy-2.4.16-installer
> .
>
> -Keegan
>

Re: [ANNOUNCE] Apache Groovy 2.4.16 released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-4-16-released


On Thu, Dec 13, 2018 at 7:17 PM Paul King  wrote:

> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.4.16 of Apache
> Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This release is a maintenance release of the GROOVY_2_4_X branch.
> While we recommend moving to the current 2.5.x releases (currently 2.5.4),
> for any users who can't upgrade to 2.5 and are using 2.4.x versions,
> we strongly recommend that you upgrade to this version.
>
> This release includes 18 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12342996
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>

Re: [ANNOUNCE] Apache Groovy 2.5.4 released

[Remko Popma]

Thanks for fixing that Paul.

On Mon, Nov 12, 2018 at 11:05 PM Paul King  wrote:

> Blog entry should have the correct version now.
>
> On Tue, Nov 13, 2018 at 12:00 AM Alessio Stalla 
> wrote:
>
>> It says 2.5.4 in the title but 2.5.3 in the actual article.
>>
>> On Mon, 12 Nov 2018 at 13:07, Remko Popma  wrote:
>>
>>> Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-4-released
>>>
>>> Please share on social media.
>>>
>>> On Monday, November 12, 2018, Paul King  wrote:
>>>
>>>> Dear community,
>>>>
>>>> The Apache Groovy team is pleased to announce version 2.5.4 of Apache
>>>> Groovy.
>>>> Apache Groovy is a multi-faceted programming language for the JVM.
>>>> Further details can be found at the http://groovy.apache.org website.
>>>>
>>>> This release is a maintenance release of the GROOVY_2_5_X branch.
>>>> It is strongly encouraged that all users using prior
>>>> versions on this branch upgrade to this version.
>>>>
>>>> This release includes 15 bug fixes/improvements as outlined in the
>>>> changelog:
>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12344270
>>>>
>>>> Sources, convenience binaries, downloadable documentation and an SDK
>>>> bundle can be found at: http://www.groovy-lang.org/download.html
>>>> We recommend you verify your installation using the information on that
>>>> page.
>>>>
>>>> Jars are also available within the major binary repositories.
>>>>
>>>> We welcome your help and feedback and in particular want
>>>> to thank everyone who contributed to this release.
>>>>
>>>> For more information on how to report problems, and to get involved,
>>>> visit the project website at https://groovy.apache.org/
>>>>
>>>> Best regards,
>>>>
>>>> The Apache Groovy team.
>>>>
>>>

Re: [ANNOUNCE] Groovy 2.5.4 Windows Installer Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-4-windows

Please share on social media.

On Monday, November 12, 2018, Keegan Witt  wrote:

> The Windows installer for Groovy 2.5.4 is available from the usual place:
> https://bintray.com/groovy/Distributions/Windows-Installer/groovy-2.5.4-
> installer.
>

Re: [ANNOUNCE] Apache Groovy 2.5.4 released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-4-released

Please share on social media.

On Monday, November 12, 2018, Paul King  wrote:

> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.4 of Apache
> Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This release is a maintenance release of the GROOVY_2_5_X branch.
> It is strongly encouraged that all users using prior
> versions on this branch upgrade to this version.
>
> This release includes 15 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123=12344270
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>

Re: [ANNOUNCE] Apache Groovy 2.5.4 released

[Remko Popma]

Nice!

Planning to do the usual Apache blog entries later today. 

Remko. 
(Shameless plug) Every java main() method deserves http://picocli.info

> On Nov 12, 2018, at 11:16, Daniel Sun  wrote:
> 
> Nice work, Paul.
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: GMavenPlus 1.6.2 Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/gmavenplus-1-6-2-released

Please share on social media.

On Mon, Oct 15, 2018 at 6:34 AM Paul King  wrote:

> Excellent work!
>
> On Mon, Oct 15, 2018 at 6:29 AM Keegan Witt  wrote:
>
>> GMavenPlus 1.6.2 has been released to Sonatype OSS
>>  and should
>> appear in Maven Central  shortly.
>> Bugs
>>
>>- Support for Java 10 bytecode (#104
>>)
>>- Support for Java 11 bytecode (#106
>>)
>>- Fixed that could error saying no Groovy dependency when it
>>shouldn't because no Groovy sources exist (ef3a3d5
>>
>> 
>>).
>>
>> Enhancements
>>
>> None
>> Potentially breaking changes
>>
>> None
>> Notes
>>
>> None
>>
>

Re: [ANNOUNCE] Groovy 2.5.3 Windows Installer Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-3-windows

Please share on social media.

On Mon, Oct 15, 2018 at 6:33 AM Paul King  wrote:

> That was quick! Thanks!
>
> On Mon, Oct 15, 2018 at 6:32 AM Keegan Witt  wrote:
>
>> The Windows installer for Groovy 2.5.3 is available from the usual
>> place:
>> https://bintray.com/groovy/Distributions/Windows-Installer/groovy-2.5.3-installer
>> .
>>
>

Re: [ANNOUNCE] Apache Groovy 2.5.3 Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-3-released

Please share on social media.

On Sun, Oct 14, 2018 at 10:09 PM Daniel.Sun  wrote:

> Great!
> Nice work, Paul :-)
>
>
>
>
> -
> Daniel Sun
> Apache Groovy committer
> Blog: http://blog.sunlan.me
> Twitter: @daniel_sun
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>

Re: [ANNOUNCE] Groovy 2.5.2 Windows Installer Released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-2-windows

please share on social media.

On Sun, Aug 19, 2018 at 12:29 PM, Paul King  wrote:

> Thanks Keegan. I added it to the download page.
>
> On Sat, Aug 18, 2018 at 3:14 PM Keegan Witt  wrote:
>
>> The Windows installer for Groovy 2.5.2 is available from the usual
>> place: https://bintray.com/groovy/Distributions/download_file?
>> file_path=groovy-2.5.2-installer.exe.
>>
>

Re: [ANNOUNCE] Apache Groovy 2.5.2 Relased

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-2-released

Please share on social media!

On Tue, Aug 14, 2018 at 4:31 PM, Paul King  wrote:

> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.2 of Apache
> Groovy.
> Apache Groovy is a multi-facet programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> This release is a maintenance release of the GROOVY_2_5_X branch.
> It is strongly encouraged that all users using prior
> versions on this branch upgrade to this version.
>
> This release includes 20 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123=12343651
> Of particular note are numerous small fixes for trait edge cases and
> some important changes for running the Groovy tools on JDK10
> (particularly on macOS). Let us know if you spot any further problems.
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>

Re: [ANNOUNCE] Apache Groovy 2.5.1 released

[Remko Popma]

Blogged: https://blogs.apache.org/groovy/entry/groovy-2-5-1-released

Please share on social media.

On Fri, Jul 13, 2018 at 11:12 PM, Paul King  wrote:

> Dear community,
>
> The Apache Groovy team is pleased to announce version 2.5.1 of Apache
> Groovy.
> Apache Groovy is a multi-faceted programming language for the JVM.
> Further details can be found at the http://groovy.apache.org website.
>
> For this release we focused on fixing up some of the usability/packaging
> issues
> that the 2.5.0 release introduced as part of supporting Groovy across
> JDKs 7 through (soon) 11. Maven/Gradle users not needing JAXB should
> now have a much improved experience building with the new version.
> (SUREFIRE users should read the release notes about some caveats).
> In 2.5.2, we should have additional changes to improve the build
> experience even further
> for JAXB users and users of the Groovy command-line tools. Please read
> the release
> notes for further information:
> http://groovy-lang.org/releasenotes/groovy-2.5.html#Groovy2.5releasenotes-
> Addendum251
>
> This release is a maintenance release of the GROOVY_2_5_X branch.
> It is strongly encouraged that all users using prior
> versions on this branch upgrade to this version.
>
> This release includes 44 bug fixes/improvements as outlined in the
> changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318123=12343365
>
> Sources, convenience binaries, downloadable documentation and an SDK
> bundle can be found at: http://www.groovy-lang.org/download.html
> We recommend you verify your installation using the information on that
> page.
>
> Jars are also available within the major binary repositories.
>
> We welcome your help and feedback and in particular want
> to thank everyone who contributed to this release.
>
> For more information on how to report problems, and to get involved,
> visit the project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
>

Re: [ANN] Announcing CodeNarc 1.2

[Remko Popma]

Blogged:
https://blogs.apache.org/groovy/entry/announce-announcing-codenarc-1-2


On Tue, Jul 10, 2018 at 3:46 AM,  wrote:

> The *CodeNarc** Team *is proud to announce the release of version *1.**2*.
>
> *CodeNarc*  is a static analysis tool for Groovy
> source code.
>
> Version *1.**2* includes 5 new rules and several enhancements and bug
> fixes. See the full details in the *release notes*
> .
>
> *New Rules*
>
>- *StaticFieldsBeforeInstanceFields* rule (convention) - Enforce that
>all static fields are above all instance fields within a class.
>- *StaticMethodsBeforeInstanceMethods* rule (convention) - Enforce
>that all static methods within each visibility level (public, protected,
>private) are above all instance methods within that same visibility level.
>- *PublicMethodsBeforeNonPublicMethods* rule (convention) - Enforce
>that all public methods are above protected and private methods.
>- *GrailsDomainStringPropertyMaxSize* rule (grails) - String
>properties in Grails domain classes have to define maximum size otherwise
>the property is mapped to VARCHAR(255) causing runtime exceptions to occur.
>- *NoJavaUtilDate* rule (convention) - Do not use java.util.Date.
>Prefer the classes in the java.time.* packages. Checks for construction of
>new java.util.Date objects.
>
> Check us out on *GitHub* !
>
> The *Grails **CodeNarc** Plugin*  has
> been updated to version *1.**2* as well.
>
>
>
>