Re: Unsupported class file major version 65 when running on java 21

[Keegan Witt]

I'm pretty sure we have that documented currently, no.

On Fri, May 17, 2024 at 2:20 AM Schalk Cronje  wrote:

> Is there a page on the doc website that has this info ?
>
> On 17/05/2024 02:42, Paul King wrote:
> > Our JDK version support is determined first and foremost by the
> > version of ASM bundled by Groovy:
> > JDK20 is supported from 4.0.6
> > JDK21 is supported from 4.0.11
> > JDK22 is supported from 4.0.16
> > JDK23 is supported from 4.0.21
> >
> > On Fri, May 17, 2024 at 10:05 AM Daniel Sun  wrote:
> >> Could you try the latest stable version, i.e. 4.0.21. As the following
> configuration shows, Java 21 is supported by Groovy 4.0.21.
> >>
> >>
> https://github.com/apache/groovy/blob/c4615cec66ed07c7f0d9c8c73ee9a6dbda147952/.github/workflows/groovy-build-test-ea.yml#L32
> >>
> >> Cheers,
> >> Daniel Sun
> >>
> >> On 2024/05/16 10:19:56 Johan Compagner via users wrote:
> >>> Hi
> >>>
> >>> We are using Jasper that bundles Groovy (4.0.8) but are getting:
> >>>
> >>> org.codehaus.groovy.GroovyBugError: BUG! exception in phase 'semantic
> >>> analysis' in source unit
> >>>
> 'calculator_fin_lay_003_f17d19ddf85e94f0e0558ad16053ed00cbb6578a89a5f69df26044d903df00e6'
> >>> Unsupported class file major version 65
> >>> at
> >>>
> org.codehaus.groovy.control.CompilationUnit$ISourceUnitOperation.doPhaseOperation(CompilationUnit.java:900)
> >>> ~[groovy-4.0.8.jar:4.0.8]
> >>> at
> >>>
> org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:692)
> >>> ~[groovy-4.0.8.jar:4.0.8]
> >>> at
> >>>
> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:666)
> >>> ~[groovy-4.0.8.jar:4.0.8]
> >>> at
> >>>
> net.sf.jasperreports.compilers.JRGroovyCompiler.compileUnits(JRGroovyCompiler.java:112)
> >>> ~[jasperreports-6.21.0.jar:6.21.0-unknown]
> >>> at
> >>>
> net.sf.jasperreports.engine.design.JRAbstractCompiler.compileReport(JRAbstractCompiler.java:231)
> >>> ~[jasperreports-6.21.0.jar:6.21.0-unknown]
> >>>
> >>>
> >>> now i tried to search and find anything related what groovy really is
> >>> supported on what version
> >>>
> >>> and i can't really find anything related to this.. I do get go gradle
> (and
> >>> you need 8.5 for java 21) but nothing really related to the actual
> groovy
> >>> version and what groovy is supporting (not from but until)
> >>>
> >>>
> >>> I do find more people with the same problem, but no real answers on
> those
> >>> questions..
> >>>
> >>> johan
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Johan Compagner
> >>> Servoy
> >>>
> --
> Schalk W. Cronjé
> Fediverse: @ysb33r@mastodon.social (general), @ysb33r@mountains.social
> (outdoor), @ysb33r@mountain.photos (photoblog), @ysb...@kraut.zone
> (videoblog), @ysb33r...@fosstodon.org (open-source work).
> Ello: @ysb33r
>
>

[ANNOUNCE] Groovy 4.0.21 and 5.0.0-alpha-8 Windows installers released

[Keegan Witt]

Windows installers for Groovy 4.0.21 and 5.0.0-alpha-8 are now available.

   - groovy-4.0.21.msi
   

   - groovy-5.0.0-alpha-8.msi
   


-Keegan

[ANNOUNCE] Groovy 4.0.20 and 5.0.0-alpha-7 Windows installers released

[Keegan Witt]

Windows installers for Groovy 4.0.20 and 5.0.0-alpha-7 are now available.

   - groovy-4.0.20.msi
   

   - groovy-5.0.0-alpha-7.msi
   

[ANNOUNCE] Groovy 3.0.20, 3.0.21, 4.0.19, and 5.0.0-alpha-6 Windows installers released

[Keegan Witt]

Windows installers for Groovy 3.0.20, 3.0.21, 4.0.19, and 5.0.0-alpha-6 are
now available.

   - groovy-3.0.20.msi
   

   - groovy-3.0.21.msi
   

   - groovy-4.0.19.msi
   

   - groovy-5.0.0-alpha-6.msi
   


-Keegan

[ANNOUNCE] Groovy 5.0.0-alpha-5 Windows installer released

[Keegan Witt]

The Windows installer for Groovy 5.0.0-alpha-5 is now available:
groovy-5.0.0-alpha-5.msi


-Keegan

[ANNOUNCE] Groovy 4.0.16, 4.0.17, 4.0.18, 5.0.0-alpha-3, and 5.0.0-alpha-4 Windows installers released

[Keegan Witt]

Windows installers for Groovy 4.0.16, 4.0.17, 4.0.18, 5.0.0-alpha-3, and
5.0.0-alpha-4 are now available.

   - groovy-4.0.16.msi
   

   - groovy-4.0.17.msi
   

   - groovy-4.0.18.msi
   

   - groovy-5.0.0-alpha-3.msi
   

   - groovy-5.0.0-alpha-4.msi
   


-Keegan

[ANNOUNCE] GMavenPlus 3.0.2

[Keegan Witt]

GMavenPlus 3.0.2 has been released. 3.0.1 released with a corrupted jar,
which is fixed in 3.0.2 (along with a version bump). The release notes
below are the consolidated release notes for both versions.

Bugs

   - [#276 ] Fix that
   enabling skipBytecodeCheck causes the Groovy version to be reported as
   not supporting the goal (thanks for reporting this @jgenoctr
   !).

Enhancements

   - [#264 ] Support
   targeting Java 21 bytecode (thanks @bmarwell
   !).
   - [#253 ] Fix
   CVE-2020-8908  and
   CVE-2023-2976 .
   - Fix CVE-2023-37460 
(242baa8
   

and 623a56f
   

   ).
   - [#279 ] Fix
   CVE-2023-42503 .

Potentially breaking changes

None.
Notes

The CVEs fixed were related to dependencies of the plugin. While I haven't
done an analysis of whether they were exploitable (since this is a Maven
plugin and not an application), it seems unlikely.

[ANNOUNCE] Groovy 4.0.15 and 5.0.0-alpha-2 Windows installers released

[Keegan Witt]

Windows installers for Groovy 4.0.15 and 5.0.0-alpha-2 are now available.

   - groovy-4.0.15.msi
   

   - groovy-5.0.0-alpha-2.msi
   


-Keegan

[ANNOUNCE] Groovy 2.5.23, 3.0.19, 4.0.14, and 5.0.0-alpha-1 Windows installer released

[Keegan Witt]

Windows installers for Groovy 2.5.23, 3.0.19, 4.0.14, and 5.0.0-alpha-1 are
now available.

   - groovy-2.5.23.msi
   

   - groovy-3.0.19.msi
   

   - groovy-4.0.14.msi
   

   - groovy-5.0.0-alpha-1.msi
   


-Keegan

[ANNOUNCE] Groovy 3.0.18 Windows installer released

[Keegan Witt]

Windows installer for Groovy 3.0.18 is now available.

https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.18/groovy-3.0.18.msi

[ANNOUNCE] Groovy 4.0.13 Windows installer released

[Keegan Witt]

Windows installer for Groovy 4.0.13 is now available.

https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.13/groovy-4.0.13.msi

-Keegan

[ANNOUNCE] GMavenPlus 3.0.0

[Keegan Witt]

Bugs

   - [#244 ] Fix Maven
   plugin validation warnings.

Enhancements

   - [#239 ] Require Maven
   3.2.5.

Potentially breaking changes

Maven's compatibility plan
 marked Maven
versions older than 3.2.5 as EOL in March 2023. Therefore, we now require
3.2.5 to move forward with the rest of the ecosystem.
Notes

Fixing the validation warnings removed some Maven dependencies from the
plugin's classpath (instead of using the ones from Maven itself). I'm not
aware of any negative consequences of this, but it's possible certain
specialized use cases might encounter changes in behavior.

[ANNOUNCE] Groovy 4.0.12 Windows installer released

[Keegan Witt]

Windows installer for Groovy 4.0.12 is now available.

https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.12/groovy-4.0.12.msi

-Keegan

[ANNOUNCE] Groovy 4.0.11 Windows installer released

[Keegan Witt]

Windows installer for Groovy 4.0.11 is now available.

https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.11/groovy-4.0.11.msi

-Keegan

[ANNOUNCE] Groovy 2.5.22 and 3.0.17 Windows installers released

[Keegan Witt]

Windows installers for Groovy 2.5.22 and 3.0.17 are now available.

2.5.22:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-2.5.22/groovy-2.5.22.msi
3.0.17:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.17/groovy-3.0.17.msi

-Keegan

[ANNOUNCE] Groovy 3.0.15, 3.0.16, 4.0.9, and 4.0.10 Windows installers released

[Keegan Witt]

Windows installers for Groovy 3.0.15, 3.0.16, 4.0.9, and 4.0.10 are now
available.

3.0.15:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.15/groovy-3.0.15.msi
3.0.16:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.16/groovy-3.0.16.msi
4.0.9:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.9/groovy-4.0.9.msi
4.0.10:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.10/groovy-4.0.10.msi

-Keegan

[ANNOUNCE] Groovy 2.5.21 and 4.0.8 Windows installers released

[Keegan Witt]

2.5.21:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-2.5.21/groovy-2.5.21.msi

4.0.8:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.8/groovy-4.0.8.msi

-Keegan

[ANNOUNCE] Groovy 2.5.20 and 3.0.14 and 4.0.7 Windows installers released

[Keegan Witt]

Windows installers for Groovy 2.5.20 and 3.0.14 and 4.0.6 are now available.

2.5.20:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-2.5.20/groovy-2.5.20.msi

3.0.14:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.14/groovy-3.0.14.msi

4.0.7:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.7/groovy-4.0.7.msi

-Keegan

[ANNOUNCE] GMavenPlus 2.1.0

[Keegan Witt]

Bugs

None.
Enhancements

   - [#230 ] Recognize JDK
   19 as a valid target bytecode.
   - [#232 ] Recognize JDK
   20 as a valid target bytecode.

Potentially breaking changes

None.
Notes

None.

[ANNOUNCE] Groovy 2.5.19 and 4.0.6 Windows installers released

[Keegan Witt]

Windows installers for Groovy 2.5.19 and 4.0.6 are now available.

2.5.19:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-2.5.19/groovy-2.5.19.msi

4.0.6:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.6/groovy-4.0.6.msi

-Keegan

[ANNOUNCE] GMavenPlus 2.0.0

[Keegan Witt]

Bugs

None.
Enhancements

   - [#210 ] Improve error
   messages when Groovy classes can't be located (avoiding the
   NullPointerExceptions that were causing confusion and instead throwing
   our own exception).
   - [#221 ] apache/groovy@
   8d19017
   #diff-5522480b605c81fc7dd50f58b857f5fc8802ea69229742441c6fdef328846062
   

caused
   an exception to be thrown for Groovy 4.0.0-RC-1 and newer when binding
   properties in a script/console/shell and
   bindPropertiesToSeparateVariables is false. The error logging when this
   happens has been improved.
   - [#223 ] Support 5, 6,
   7, 8, and 1.9 arguments to targetBytecode so that validation doesn't
   unexpectedly fail since it uses the maven.compiler.target property and
   these arguments are valid for javac.

Potentially breaking changes

This release requires Java 8 and drops support for Java 7. This was
necessary to update dependencies which fix vulnerabilities. Specifically,
in maven-archiver. At the time of release, the following dependencies were
not compatible with Java 7

   - org.apache.commons:commons-compress
   - org.codehaus.plexus:plexus-archiver
   - org.apache.maven:maven-archiver
   - org.codehaus.plexus:plexus-io
   - org.codehaus.plexus:plexus-utils

This is not the first breaking release, but it is the first breaking
release to follow the semver  conventions.
Notes

None.

[ANNOUNCE] Groovy 3.0.13 Windows installer released

[Keegan Witt]

Windows installer for Groovy 3.0.13 is now available.

https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.13/groovy-3.0.13.msi

-Keegan

[ANNOUNCE] Groovy 4.0.5 Windows installer released

[Keegan Witt]

Windows installer for Groovy 4.0.5 is now available.

https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.5/groovy-4.0.5.msi

-Keegan

[ANNOUNCE] Groovy 2.5.18, 3.0.12, and 4.0.4 Windows installers released

[Keegan Witt]

Windows installers for Groovy 2.5.18, 3.0.12, and 4.0.4 are now available.

2.5.18:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-2.5.18/groovy-2.5.18.msi
3.0.12:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.12/groovy-3.0.12.msi
4.0.4:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.4/groovy-4.0.4.msi

-Keegan

[ANNOUNCE] Groovy 2.5.17, 3.0.11, and 4.0.3 Windows installers released

[Keegan Witt]

Windows installers for Groovy 2.5.17, 3.0.11, and 4.0.3 are now available.

2.5.17:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-2.5.17/groovy-2.5.17.msi
3.0.11:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-3.0.11/groovy-3.0.11.msi
4.0.3:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.3/groovy-4.0.3.msi

-Keegan

[ANNOUNCE] Groovy 4.0.2 Windows installer released

[Keegan Witt]

Windows installer for Groovy 4.0.2 is now available:
https://groovy.jfrog.io/ui/native/dist-release-local/groovy-windows-installer/groovy-4.0.2/groovy-4.0.2.msi

-Keegan

Re: [ANNOUNCE] Groovy 4.0.1 and 3.0.10 Windows installers released

[Keegan Witt]

Apologies, it looks like the link pattern isn't the same as previous
releases (I'm not sure why at the moment).  The correct links are

4.0.1:
https://groovy.jfrog.io/artifactory/dist-release-local/groovy-windows-installer/groovy-4.0.1/groovy-4.0.1.msi
3.0.10:
https://groovy.jfrog.io/artifactory/dist-release-local/groovy-windows-installer/groovy-3.0.10/groovy-3.0.10.msi

On Wed, Mar 9, 2022 at 9:56 AM Keegan Witt  wrote:

> 4.0.1:
> https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.1/groovy-4.0.1.msi
> 3.0.10:
> https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-3.0.10/groovy-3.0.10.msi
>
> -Keegan
>

[ANNOUNCE] Groovy 4.0.1 and 3.0.10 Windows installers released

[Keegan Witt]

4.0.1:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.1/groovy-4.0.1.msi
3.0.10:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-3.0.10/groovy-3.0.10.msi

-Keegan

[ANNOUNCE] Groovy 4.0.0 Windows installer released

[Keegan Witt]

 Windows installer fro Groovy 4.0.0 is now available:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.0/groovy-4.0.0.msi
.

-Keegan

[no subject]

[Keegan Witt]

Windows installer for Groovy 4.0.0-rc-2 is now available:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.0-rc-2/groovy-4.0.0-rc-2.msi

-Keegan

[ANNOUNCE] Groovy 4.0.0-rc-1 Windows installer released

[Keegan Witt]

Windows installer for Groovy 4.0.0-rc-1 is now available:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.0-rc-1/groovy-4.0.0-rc-1.msi

-Keegan

[ANNOUNCE] GMavenPlus 1.13.1

[Keegan Witt]

 Bugs

   - [#203 ] Using
   bindAllProjectProperties and bindSessionUserOverrideProperties together
   can cause an NPE.

Enhancements

None
Potentially breaking changes

None.
Notes

None.

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

-Keegan

[ANNOUNCE] Groovy 4.0.0-beta-2 Windows installer released

[Keegan Witt]

Windows installer fro Groovy 4.0.0-beta-2 is now available:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.0-beta-2/groovy-4.0.0-beta-2.msi

-Keegan

[ANNOUNCE] GMavenPlus 1.13.0

[Keegan Witt]

 Bugs

None.
Enhancements

   - [#196 ] Add support
   for targetting Java 17.
   - [#198 ] Add support for
   targetting Java 18.
   - [#188 /#193
   ] Update Ant from 1.10.8
   to 1.10.11.

Potentially breaking changes

None.
Notes

None.

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.


-Keegan

[ANNOUNCE] Groovy 2.5.15, 3.0.9, and 4.0.0-beta-1 Windows installers released

[Keegan Witt]

Windows installers for the latest Groovy releases are now available.

2.5.15:
https://groovy.jfrog.io/artifactory/dist-release-local/groovy-windows-installer/groovy-2.5.15/groovy-2.5.15.msi
3.0.9:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-3.0.9/groovy-3.0.9.msi
4.0.0-beta-1:
https://groovy.jfrog.io/native/dist-release-local/groovy-windows-installer/groovy-4.0.0-beta-1/groovy-4.0.0-beta-1.msi

-Keegan

[ANNOUNCE] Groovy 3.0.8 and 4.0.0-alpha-3 Windows installers released

[Keegan Witt]

Windows installers for the latest Groovy releases are now available. These
are the first releases to be on our Bintray replacement, now that it's been
sunset
.
All versions previously released to Bintray can be found in directories
under
https://groovy.jfrog.io/ui/repos/tree/General/dist-release-local%2Fgroovy-windows-installer
.


   - 3.0.8:
   
https://groovy.jfrog.io/artifactory/dist-release-local/groovy-windows-installer/groovy-3.0.8/groovy-3.0.8.msi
   - 4.0.0-alpha-3:
   
https://groovy.jfrog.io/artifactory/dist-release-local/groovy-windows-installer/groovy-4.0.0-alpha-3/groovy-4.0.0-alpha-3.msi

-Keegan

Re: [ANNOUNCE] Groovy 2.4.21, 2.5.14, and 3.0.7 Windows installers released

[Keegan Witt]

Ah, Paul reminded me where that file is and I actually fixed the link back
in 2019 on master, but forgot to cherry-pick it over.  I'll get the link
fixed.  Thanks for reporting.

-Keegan

On Tue, Jan 12, 2021 at 8:19 PM Keegan Witt  wrote:

> The latest install links are on this page:
> https://groovy.apache.org/download.html
>
> There's also the parent page in Bintray that has all the files:
> https://bintray.com/groovy/Distributions/Windows-Installer
>
> -Keegan
>
> On Mon, Dec 21, 2020 at 4:41 AM Mike M  wrote:
>
>> A novice colleague had trouble installing Groovy in Windows following the
>> instructions here:
>> https://groovy-lang.org/install.html#_installation_on_windows
>> Basically this section links to a non existing page.  A link to bintray
>> in this section would be helpful.
>> The Apache Groovy programming language - Install Groovy
>> <https://groovy-lang.org/install.html#_installation_on_windows>
>> First, Download a binary distribution of Groovy and unpack it into some
>> file on your local file system. Set your GROOVY_HOME environment variable
>> to the directory you unpacked the distribution.. Add GROOVY_HOME/bin to
>> your PATH environment variable.. Set your JAVA_HOME environment variable to
>> point to your JDK. On OS X this is /Library/Java/Home, on other unixes its
>> often /usr/java etc.
>> groovy-lang.org
>>
>> --
>> *From:* Keegan Witt 
>> *Sent:* 04 December 2020 05:48
>> *To:* users@groovy.apache.org 
>> *Subject:* [ANNOUNCE] Groovy 2.4.21, 2.5.14, and 3.0.7 Windows
>> installers released
>>
>> Windows installers for the latest Groovy releases are now available.
>>
>> 2.4.21:
>> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.21.msi
>> 2.5.14:
>> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.14.msi
>> 3.0.7:
>> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.7.msi
>>
>> -Keegan
>>
>

Re: [ANNOUNCE] Groovy 2.4.21, 2.5.14, and 3.0.7 Windows installers released

[Keegan Witt]

The latest install links are on this page:
https://groovy.apache.org/download.html

There's also the parent page in Bintray that has all the files:
https://bintray.com/groovy/Distributions/Windows-Installer

-Keegan

On Mon, Dec 21, 2020 at 4:41 AM Mike M  wrote:

> A novice colleague had trouble installing Groovy in Windows following the
> instructions here:
> https://groovy-lang.org/install.html#_installation_on_windows
> Basically this section links to a non existing page.  A link to bintray in
> this section would be helpful.
> The Apache Groovy programming language - Install Groovy
> <https://groovy-lang.org/install.html#_installation_on_windows>
> First, Download a binary distribution of Groovy and unpack it into some
> file on your local file system. Set your GROOVY_HOME environment variable
> to the directory you unpacked the distribution.. Add GROOVY_HOME/bin to
> your PATH environment variable.. Set your JAVA_HOME environment variable to
> point to your JDK. On OS X this is /Library/Java/Home, on other unixes its
> often /usr/java etc.
> groovy-lang.org
>
> --
> *From:* Keegan Witt 
> *Sent:* 04 December 2020 05:48
> *To:* users@groovy.apache.org 
> *Subject:* [ANNOUNCE] Groovy 2.4.21, 2.5.14, and 3.0.7 Windows installers
> released
>
> Windows installers for the latest Groovy releases are now available.
>
> 2.4.21:
> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.21.msi
> 2.5.14:
> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.14.msi
> 3.0.7:
> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.7.msi
>
> -Keegan
>

GMavenPlus 1.12.1 Released

[Keegan Witt]

GMavenPlus 1.12.1 
has been released.
Bugs

   - [#186 ] Certain AST
   transformations had classloader issues because 1.12.0 was no longer setting
   the context classloader.

Enhancements

   - Update Jansi to 2.x.

Potentially breaking changes

The Jansi upgrade should generally be compatible, but could cause issues
with scripts that were using Jansi 1.x specific classes.
Notes

None.

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.


-Keegan

GMavenPlus 1.12.0 Released

[Keegan Witt]

 Bugs

   - [#183 ] The
   classloader project dependencies are loaded onto is reused between modules,
   so each module was a superset of all modules that preceded it. Also, the
   console, execute, and shell mojos didn't pass the classloader to use into
   the instantiated GroovyConsole/GroovyShell, so it accidentally was using
   the plugin classloader, even when configured to use PROJECT_ONLY
   classpath.

Enhancements

None
Potentially breaking changes

This should be a non-breaking change (except for unusual situations that
were relying on the previous incorrect behavior). However, since it's a
significant change, I'm bumping the version by more than just the patch
version.
Notes

None

[ANNOUNCE] Groovy 4.0.0-alpha-2 Windows installer released

[Keegan Witt]

Groovy 4.0.0-alpha-2 Windows installer now available from its usual place:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-4.0.0-alpha-2.msi
.

-Keegan

[ANNOUNCE] Groovy 2.4.21, 2.5.14, and 3.0.7 Windows installers released

[Keegan Witt]

Windows installers for the latest Groovy releases are now available.

2.4.21:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.21.msi
2.5.14:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.14.msi
3.0.7:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.7.msi

-Keegan

GMavenPlus 1.11.1 Released

[Keegan Witt]

 Bugs

   - Fixes IllegalArgumentException when consoleScript parameter was loaded
   from POM rather than command line property.

Enhancements
None
Potentially breaking changes
None
Notes

None

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

GMavenPlus 1.11.0 Released

[Keegan Witt]

https://github.com/groovy/GMavenPlus/releases/tag/1.11.0

Bugs

None
Enhancements

   - Change JDK compatibility check to also account for Java 16.
   - Some tweaks for Groovy 4 (most notably, invokedynamic is enabled by
   default for Groovy 4 and cannot be disabled).
   - New parameter (attachGroovyDocAnnotation) to enable attaching
   GroovyDoc annotation.
   - New parameter (parallelParsing) to enable parallel parsing (enabled by
   default with Groovy 4).
   - Remove previewFeatures parameter from stub generation goals, since
   it's not used there.

Potentially breaking changes

   - If you were using the previewFeatures parameter without also including
   a compilation goal that would make that config valid, the build will fail
   because it's no longer a valid parameter. The fix would be to move that
   configuration to the appropriate execution(s).

Notes

None

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

[ANNOUNCE] Groovy 3.0.6 and 4.0.0-alpha-1 Windows installers released

[Keegan Witt]

3.0.6:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.6.msi
4.0.0-alpha-1:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-4.0.0-alpha-1.msi

-Keegan

Re: 3.0.x Windows installers released

[Keegan Witt]

Edit on 6:
I think I misread this originally.  Actually the file association thing
doesn't apply in this case, that's an issue with the shortcuts.  The issue
I think is that before we were including groovy.exe (the native binaries)
and now we're not, we're just providing batch and VB script files.  When
executed from inside cmd.exe, invoking just "groovy" works fine, since the
shell is able to do the interpretation from groovy to groovy.bat.  But this
doesn't work from inside Java because it doesn't have the shell to do any
interpretation.  While this is related to the file association issue (in
that the issue exists because there are no binaries), it is a use case I
had not considered.  For what I tend to do, I just wanted to be able to
click Groovy Console in the start menu and not have an annoying cmd.exe
window pop open, so a VB script was sufficient for that.  It's feeling like
I'm going to have to re-introduce some kind of binary wrapper.

-Keegan

On Tue, Sep 29, 2020 at 2:33 AM Keegan Witt  wrote:

> 1.
> That's correct.  There were a few discussions about why I thought we
> should do this.  Here's a short summary: Most of the modules included you
> can just use @grab for anyway, the few others where that wouldn't apply
> (GroovyServ, Grengine) seemed low usage.  Scriptom was the only other one
> in this category that I've heard folks actually use.  But multiple of the
> installed extras hadn't been updated in years (and some never will).  It's
> been 10 1/2 years since the last Scriptom release.  I know Scriptom is
> specific to Windows, but I also thought it'd be good to be somewhat
> consistent with the environment provided between platforms, which would
> help folks writing scripts targeting different platforms have some
> consistency.
>
> 2.
> I opened a PR to update the installer links (
> https://github.com/apache/groovy-website/pull/25).
>
> 3.
> Yes, as noted in the 3.0 announcement email, when the WiX version replaced
> the NSIS version (when 3.0 first released), the NSIS version should be
> uninstalled before installing the new version.
>
> 4.
> There are no native binaries included anymore, so there's nothing x86 or
> x64 specific about it.  One of the things I didn't like about how the old
> installer worked is it would detect your current Java (from JAVA_HOME if I
> recall correctly) and those would be the binaries copied over.  But this
> seemed a fragile way to do it to me, since you might have several JDKs
> installed, and on different architectures.  There also wasn't really any
> reason to have 64 bit binaries in my view, since they're just wrappers for
> calling java.exe and will never need so much memory that they'd benefit
> from being 64 bit.
>
> 5.
> This kept the installer logic simple.  I'm not sure the best practice
> about the installation directory when the thing being installed is platform
> independent.  I think I should be able to use the variable for the 64 bit
> program files directory if available, if you think that'd be better.  It
> seemed somewhat an arbitrary choice.
>
> 6. (the question about .bat)
> I think this is related to the known issue with needing vbs files to have
> the appropriate file association (
> https://github.com/groovy/groovy-wix/issues/2).  I've been trying to find
> a better solution for this, without needing to have something as
> heavy-weight as the native binaries we used to use, which have logic about
> JAVA_HOME, etc.  I haven't found a better solution yet, I may have to
> revive the native binaries (or do something similar).  I've documented my
> investigations in that issue.  I also mention there how you can check and
> fix your file associations there.
>
> 7. (the question about execute)
> I don't quite understand this question.  The "execute" thing you're
> showing is a feature of the JDK.  GroovyScriptEngine is included in Groovy
> and there's no reason you shouldn't be able to use this instead if you wish.
>
>
> A bit of a discussion for the dev mailing list I suppose, but what do we
> consider the official position on Scriptom?  Should it be considered
> deprecated?  We copied the stuff over from Codehaus after the shutdown, but
> it hasn't been touched since (and I think hadn't been touched in a while
> even before the move).  If it's something we want to continue to support, I
> think we need to do some updates, like updating to the latest Jacob.  Some
> questions I'd have if it were to be revived (bearing in mind I'm not really
> familiar with these features):
>
>1. Should we drop the Office modules?  Or if not, we might need to
>update for newer Office versions.
>2. Should the IE6 module be dropped?  IE6 is pretty dead at this point.
>
> I'm willing to reconsider the decisio

Re: 3.0.x Windows installers released

[Keegan Witt]

lts the install under *program files (x86)* – suggesting a
>32-bit implementation only.   Only the ‘custom’ option allows it to be put
>somewhere else.
>
>
>
> I then noticed that if I execute this in groovysh or in the groovyConsole:
>
> *“groovy -v”.execute().waitForProcessOutput(System.out, System.err)*
>
> Exception thrown
>
> java.io.IOException: Cannot run program "groovy": CreateProcess error=2,
> The system cannot find the file specified
>
>at ConsoleScript5.run(ConsoleScript5:1)
>
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot
> find the file specified
>
>
>
> *But this works*
>
>
>
> *“groovy.bat -v”.execute().waitForProcessOutput(System.out, System.err)*
>
> Groovy Version: 3.0.3 JVM: 1.8.0_162 Vendor: Oracle Corporation OS:
> Windows 10
>
>
>
> Does this suggest that the installed groovy is 32-bit when my computer and
> JDK are both 64-bit?  My older groovy installs (going back to 2.0.4) would
> all work.
>
>
>
> PS – *Why call groovy using “execute” rather than **GroovyScriptEngine**?*
> Well some of these called scripts use *System.exit (error-number)* and if
> I use the ScriptEngine or similar, it causes my script to exit as well!
>
>
>
> Merlin Beedell
>
> 0800 280 0525 / +44 (0)207 045 0520
>
> DDI: +44 (0)207 045 0528
>
> Mob: +44 (0)7876 226865
>
> *Cryoserver: A focused, flexible email archive delivered by experts*
>
>
>
> *From:* Guillaume Laforge 
> *Sent:* 23 July 2020 12:51 PM
> *To:* users@groovy.apache.org; Paul King 
> *Subject:* Re: [ANNOUNCE] Groovy 2.4.20, 2.5.13, and 3.0.5 Windows
> installers released
>
>
>
> Combo!
>
>
>
> Le jeu. 23 juil. 2020 à 12:13, Paul King  a écrit :
>
> Nice!
>
>
>
> On Thu, Jul 23, 2020 at 3:07 PM Keegan Witt  wrote:
>
> 2.4.20:
> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.20.msi
> 2.5.13:
> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.13.msi
>
> 3.0.5:
> https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.5.msi
>
>
>
> -Keegan
>
>

GMavenPlus 1.10.1 Released

[Keegan Witt]

https://github.com/groovy/GMavenPlus/releases/tag/1.10.1
Bugs

None
Enhancements

   - Ability to override classes used to generate GroovyDoc (#91
   )
   - Ability to override GStringTemplates used for GroovyDoc (#105
   )
   - Ability to bind overridden properties (by binding project properties
   and/or session user properties) (#72
   )
   - Ability to load a script when launching GroovyConsole (#165
   )

Notes
Not tied to the release, but one notable addition to the documentation is
examples of how GMavenPlus can be used with Spock & JUnit 4 and Spock &
JUnit 5.

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

Re: Installation Problem on Windows

[Keegan Witt]

I'm sorry you had trouble.  Was the issue with PATH?  Or with vbs/bat file
associations?

-Keegan

On Tue, Aug 11, 2020 at 11:10 AM Kristine  wrote:

>
> Fixed by editing environment variables
>

Re: How to generate groovydoc?

[Keegan Witt]

I think we can close that Jira.  Only groovysh uses Jansi anymore I
believe.  It's no longer referenced in groovydoc.

This link seems to be missing from the tools section of the main page, but
it is up to date last I knew and covers how to invoke groovydoc from the
command line.  http://groovy-lang.org/groovydoc.html

Alternatively, you could make a small Gradle, Maven, or Ant file to run it
for you as others have suggested.

-Keegan

On Thu, Jul 30, 2020 at 1:15 PM Daniil Ovchinnikov <
daniil.ovchinni...@jetbrains.com> wrote:

> For more info see
> https://youtrack.jetbrains.com/issue/IDEA-80697#focus=Comments-27-3935496.0-0
>
> —
>
> Daniil Ovchinnikov
> JetBrains
>
> > On 30 Jul 2020, at 20:10, Fernando Franzini 
> wrote:
> >
> > Hi Keith
> >
> > What version of IntelliJ are you using?
> > 2020.xx
> >
> > The option to generate Groovydoc is still there for me in 2020.1
> Ultimate.
> > Where? Which menu?
> >
> > Att,
> >
> > Fernando Franzini - Blog
> >
> >
> >
> > Em qui., 30 de jul. de 2020 às 13:42, Keith Suderman <
> suder...@cs.vassar.edu> escreveu:
> > What version of IntelliJ are you using?  The option to generate
> Groovydoc is still there for me in 2020.1 Ultimate.
> >
> > If you are not using a build tool like Gradle or Maven then you can also
> generate documentation with the groovydoc command:
> >
> > $> groovydoc -sourcepath=./src/main/groovy -d output com.example
> >
> > This will generate the GroovyDoc for the package com.example, assumes
> your source code is in ./src/main/groovy, and writes the HTML files to a
> directory named "output".
> >
> > Cheers,
> > Keith
> >
> >
> >> On Jul 30, 2020, at 8:42 AM, Fernando Franzini <
> fernandofranz...@gmail.com> wrote:
> >>
> >> Hi Paul
> >>
> >> I paid intelliJ ultimate and the option to generate groovydoc has been
> removed, so I need to generate it manually.
> >> Do you recommend any article or documentation with groovy 3.x?
> >>
> >> Regards.
> >> Att,
> >>
> >> Fernando Franzini - Blog
> >>
> >>
> >>
> >> Em qui., 30 de jul. de 2020 às 09:00, Paul King 
> escreveu:
> >> There is the groovydoc command from the commandline but you'll likely
> want to use the groovydoc integration from your build tool of choice.
> >>
> >> Cheers, Paul.
> >>
> >> On Thu, Jul 30, 2020 at 8:57 PM Fernando Franzini <
> fernandofranz...@gmail.com> wrote:
> >> Hi Groovy Folks
> >> My projects contain java and groovy classes. How do I generate the
> groovy doc for all of them?
> >> Regards
> >> Att,
> >>
> >> Fernando Franzini - Blog
> >>
> >
>
>

GMavenPlus 1.9.1 Released

[Keegan Witt]

 Bugs

None
Enhancements

   - Add a property to skip script execution (#162
   )

Potentially breaking changesNone
Notes None

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

[ANNOUNCE] Groovy 2.4.20, 2.5.13, and 3.0.5 Windows installers released

[Keegan Witt]

2.4.20:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.20.msi
2.5.13:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.13.msi
3.0.5:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.5.msi

-Keegan

[ANNOUNCE] Groovy 2.5.12 and 3.0.4 Windows Installers Released

[Keegan Witt]

New Groovy installers for Windows released:

2.5.12:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.12.msi
3.0.4:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.4.msi

-Keegan

[ANNOUNCE] Groovy 2.5.11 and 3.0.3 Windows Installers Released

[Keegan Witt]

New Groovy installers for windows released:

2.5.11:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.11.msi
3.0.3:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.3.msi

-Keegan

GMavenPlus 1.9.0 Released

[Keegan Witt]

GMavenPlus 1.9.0 has been released.  As mentioned in the release notes
, this release
includes:
Bugs

None
Enhancements

   - Support for Java 14 (#152
   ).
   - Support for Java 15 (#153
   ) (will be available in
   Groovy 3.0.3).
   - Add skipBytecodeCheck property and parameter, so if a Java version
   comes out the plugin doesn't recognize, you can use it without having to
   wait for an update.
   - Use *groovy.ant.AntBuilder* instead of *groovy.util.AntBuilder* (if
   available).

Potentially breaking changes

   - maven.groovydoc.skip property was renamed to skipGroovydoc so it
   matches the pattern of the other properties and won't seem to imply it's a
   property for a standard Maven plugin.
   - Using *groovy.ant.AntBuilder* instead of *groovy.util.AntBuilder*
   (when available on classpath).
   - Bundling Ant *1.10.7* instead of *1.10.5*.
   - Bundling Ivy *2.5.0* instead of *2.4.0*.

Notes

   - Now officially requires Java 7 instead of 6. This is not a breaking
   change, however, since this was actually already required because of
   plexus-classworlds. This just wasn't discovered until an enforcer rule was
   added to check bytecode versions of dependencies.

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

[ANNOUNCE] Groovy 2.4.19, 2.5.10, and 3.0.2 Windows Installers Released

[Keegan Witt]

I released these a few days ago, but didn't send messaging out.

3.0.2:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.2.msi
2.5.10:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.10.msi
2.4.19:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.19.msi

-Keegan

Re: Groovy branches and Docker images

[Keegan Witt]

I have not.  Andrei's was the only response I'd gotten (thank you for that,
Andrei).

-Keegan

On Mon, Mar 9, 2020 at 4:20 AM Jochen Theodorou  wrote:

> On 04.03.20 15:09, Keegan Witt wrote:
> > When Groovy 3.0.0 was released, I stopped maintaining 2 branches in
> > docker-groovy <https://github.com/groovy/docker-groovy> and have kept
> > just the latest stable branch.  I'm wondering now if folks have a need
> > for me to maintain Docker images for both 2.5 and 3.0 (though I presume
> > not 2.4 since nobody has asked me for it yet).
> >
> > I'm not sure if anyone is actually using these images, and if so, what
> > their needs are.  So if someone is using them and can provide insight
> > into whether my recent change negatively impacts them, please let me
> know.
>
> did you receive any feedback private?
>
> bye Jochen
>
>

Groovy branches and Docker images

[Keegan Witt]

When Groovy 3.0.0 was released, I stopped maintaining 2 branches in
docker-groovy  and have kept just
the latest stable branch.  I'm wondering now if folks have a need for me to
maintain Docker images for both 2.5 and 3.0 (though I presume not 2.4 since
nobody has asked me for it yet).

I'm not sure if anyone is actually using these images, and if so, what
their needs are.  So if someone is using them and can provide insight into
whether my recent change negatively impacts them, please let me know.

-Keegan

[ANNOUNCE] Groovy 3.0.1 Windows Installer Released

[Keegan Witt]

 The Windows installer for Groovy 3.0.1 is now available from Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.1.msi
.

There are still a few little things to get done (such as
internationalization) with the new installer.  Let me know if you encounter
any issues.

-Keegan

[ANNOUNCE] Groovy 3.0.0 Windows Installer Released

[Keegan Witt]

The Windows installer for Groovy 3.0.0 is now available from Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0.msi
.

As I believe I've mentioned previously, I planned on ending producing the
NSIS .exe installers and only providing the Wix based .msi installers,
starting with Groovy 3.  These are closer to vanilla Groovy, and don't any
of the supplemental content, namely,

   - Native executable wrappers (i.e. groovy.exe, groovyw.exe)
   - EasyB
   - Galyk
   - Gant
   - GMock
   - GPars
   - GREngine
   - Griffon
   - GroovyServ
   - Scriptom
   - Spock

A number of these projects haven't been updated in quite some time, and
most (like Spock) would be better provided using Grape
, so
that it's decoupled from Groovy releases and more platform independent
(since most platforms won't include these libraries).  If for some reason,
someone really needs this content, or really can't use the msi installer,
I'd like to have a dialog about your needs and find a solution that reduces
the maintenance overhead.

-Keegan

[ANNOUNCE] Groovy 3.0.0-rc-3 Windows Installers Released

[Keegan Witt]

 The Windows installers for Groovy 3.0.0-rc-2 are now available from
Bintray.  It is available as

   - The original exe installer, built with NSIS:
   
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-rc-3-installer.exe
   - The new msi installer, built with WiX:
   
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-rc-3.msi

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

[ANNOUNCE] Groovy 2.5.9 Windows Installers Released

[Keegan Witt]

 The Windows installers for Groovy 2.5.9 are now available from Bintray.
It is available as

   - The original exe installer, built with NSIS:
   
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.9-installer.exe
   - The new msi installer, built with WiX:
   
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.9.msi

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

[ANNOUNCE] Groovy 2.4.18 Windows Installers Released

[Keegan Witt]

 The Windows installers for Groovy 2.4.18 are now available from Bintray.
It is available as

   - The original exe installer, built with NSIS:
   
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.18-installer.exe
   - The new msi installer, built with WiX:
   
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.4.18.msi

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

[ANNOUNCE] Groovy 3.0.0-rc-2 Windows Installer Released

[Keegan Witt]

 The Windows installer for Groovy 3.0.0-rc2 is now available from Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-rc-2-installer.exe
.

I've again included a preview of an msi built with WiX, which I'm seeking
feedback on:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-rc-2+%28preview+installer%29.msi
.

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

GMavenPlus 1.8.1 Released

[Keegan Witt]

GMavenPlus 1.8.1 has been released.  This release includes
Bugs

   - #147  Change sourcesets
   internal storage from HashSet to TreeSet, to avoid unpredictable Groovy
   compiler output.
   - #145  Disable system
   exits by default, to avoid potential thread safety issues.

Enhancements

None
Potentially breaking changes

   - #145  Changes the
   default of not allowing System.exits to allowing them.

Notes

None

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

[ANNOUNCE] Groovy 3.0.0-rc-1 Windows Installer Released

[Keegan Witt]

 The Windows installer for Groovy 3.0.0-rc1 is now available from Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-rc-1-installer.exe
.

I've again included a preview of an msi built with WiX, which I'm seeking
feedback on:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-rc-1+%28preview+installer%29.msi
.

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

-Keegan

GMavenPlus 1.8.0 Released

[Keegan Witt]

 This was a small release, offering one new feature.  It bumped up the
minor version because it may require you to adjust your POM to upgrade. Bugs

   - None

Enhancements

   - Allow for invocation using only project classpath (#140
   ). This is accomplished
   with PLUGIN_ONLY.

Potentially breaking changes #140


If you were using useSharedClasspath before, you will need to replace it
with new values. In most cases, this would be
usedSharedClasspath includeClasspath
true PROJECT_AND_PLUGIN
false PROJECT_ONLY

Another notable difference is that when using this new configuration
parameter in *compile*, *compileTests*, *generateStubs*, or
*generateTestStubs* goals, now also uses the configurator to add the
project dependencies to the classpath with the plugin's dependencies.
Previously, this only happened in the goals other than the ones mentioned.
Notes

None

*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

[ANNOUNCE] Groovy 3.0.0-beta-3 Windows Installer Released

[Keegan Witt]

The Windows installer for Groovy 3.0.0-beta-3 is now available from
Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-beta-3-installer.exe
.

I've again included a preview of an msi built with WiX, which I'm seeking
feedback on:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-beta-3+%28preview+installer%29.msi

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

-Keegan

[ANNOUNCE] Groovy 2.5.8 Windows Installer Released

[Keegan Witt]

The Windows installer for Groovy 2.5.8 is now available from Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.8-installer.exe
.

I've again included a preview of an msi built with WiX, which I'm seeking
feedback on:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.8+%28preview+installer%29.msi

Be aware that you need to fully uninstall the NSIS based Groovy
installation before
installing with an MSI installer.

-Keegan

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

[Keegan Witt]

The Windows installer for Groovy 3.0.0-beta-2 is now available from
Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-beta-2-installer.exe
.

I've again included a preview of an msi built with WiX, which I'm seeking
feedback on:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-beta-2+%28preview+installer%29.msi

Be aware that you need to fully uninstall the NSIS based Groovy installation
before installing with an MSI installer.

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

[Keegan Witt]

 The Windows installer for Groovy 2.5.7 is now available from Bintray:
https://bintray.com/groovy/Distributions/Windows-Installer/groovy-2.5.7-installer
.

The Windows installer for Groovy 3.0.0-beta-1 is now available from
Bintray:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-beta-1-installer.exe
.

These are also the first releases where I've published a preview of Windows
Installers created with the WiX Toolset.  I invite you to try them out and
provide any feedback you might have.  It's my intention to eventually
replace the current NSIS-based installer with this installer.  I believe it
to be reasonably stable.  I've personally been using these instead of the
NSIS based installer for a while now.  Here are the links to those
installers:
3.0.0-beta-1:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-3.0.0-beta-1+%28preview+installer%29.msi
2.5.7:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.7+%28preview+installer%29.msi

Be aware that you need to fully uninstall the NSIS based Groovy
installation before installing with an MSI installer.

-Keegan

GMavenPlus 1.7.0 Released

[Keegan Witt]

GMavenPlus 1.7.0 has been released to Sonatype OSS
 and should appear in
Maven Central  shortly.  This release includes

Bugs


   - Fix executing script from URL in Groovy older than 1.7.0 (#131
   )
   - Use unique configuration names for every mojo, so goals don't conflict
   (#120 )

Enhancements

   - Support Java 13 (#122 )

Potentially breaking changes

#120  corrects an
inadvertent breaking change made in 1.6.0 with #31
/#58
. Additionally,
groovydocJavaSources has been renamed to testGroovydocJavaSources for
testGroovydoc.  Here are those changes:
  1.5 1.6 1.7
addStubSources stubsOutputDirectory outputDirectory stubsOutputDirectory
addTestStubSources testStubsOutputDirectory outputDirectory
testStubsOutputDirectory
compileTests/testCompile testOutputDirectory outputDirectory
testOutputDirectory
generateStubs stubsOutputDirectory outputDirectory stubsOutputDirectory
generateTestStubs/testGenerateStubs testStubsOutputDirectory outputDirectory
testStubsOutputDirectory
groovydocTests/testGroovydoc groovydocJavaSources groovydocJavaSources
testGroovydocJavaSources
removeStubs stubsOutputDirectory outputDirectory stubsOutputDirectory
removeTestStubs testStubsOutputDirectory outputDirectory
testStubsOutputDirectory

In addition, unused parameters have been removed:

addSources

   - skipTests
   - testSources

addStubSources

   - skipTests
   - sources
   - testSources

addTestSources

   - outputDirectory
   - skipTests
   - sources

addTestStubSources

   - sources
   - testSources

compile

   - skipTests
   - testSources

compileTests

   - sources

console

   - skipTests

execute

   - skipTests

generateStubs

   - skipTests
   - testSources

generateTestStubs

   - sources

groovydoc

   - skipTests
   - testSources
   - testGroovyDocOutputDirectory

groovydocTests

   - skipTests
   - sources

removeStubs

   - skipTests
   - sources
   - testSources

removeTestStubs

   - sources
   - testSources

shell

   - skipTests

Lastly, addTestStubSources and removeTestStubs now respect the skipTests
flag, for consistency.
Notes

None
*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list , GitHub issues
, or Slack
.

Enjoy!

GMavenPlus 1.6.3 Released

[Keegan Witt]

GMavenPlus 1.6.3 has been released to Sonatype OSS
 and should appear in
Maven Central  shortly.  This release includes

Bugs

None
Enhancements

   - Ability to use Groovy from plugin dependencies (creates a single
   classpath with plugin and project dependencies) (#64
    & #86
   )
   - Support for Java 13 bytecode (#123
   )
   - Log executed scripts (#119
   )
   - Log message from exception cause (#112
   )

Potentially breaking changes

None
Notes

The feature for #64 & #86 is controversial for me.  In my humble opinion, I
think it's usually a sign of bad build practices if you have a need for
this feature.  It's potentially dangerous, as if there are differing
dependency versions between GMavenPlus's dependencies and your project
dependencies, you may have compiled against a version that is different
than expected (and won't match runtime -- watch out for
NoClassDefFoundError).  However, since multiple users have requested this
option, and since the philosophy of this project is to provide the user
with reasonable defaults but full control, I've acquiesced to the request.
The defaults retain the same behavior as the previous release.
*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list (http://groups.google.com/group/gmavenplus), GitHub issues (
https://github.com/groovy/GMavenPlus/issues), or Slack (
https://groovy-community.slack.com/messages/C2SLAV9FY/).

Enjoy!

-Keegan

Re: New Groovy Windows installer

[Keegan Witt]

Yea, I've thought about renaming the repo to groovy-wix-installer for that
reason.

As for multiplatform installers, there is izpack <http://izpack.org/>, but
I thought it best to use a more native installer when doing things like
modifying PATH (from what I saw people were calling VB or Python scripts to
handle that with izpack -- ugly and potentially dangerous).

On Mon, Feb 18, 2019 at 6:46 AM Merlin Beedell 
wrote:

> I was a bit confused, as WIX is a web site design and hosting service:
> www.wix.com.
>
>  But now I see your link, and it is *WiX Toolset* – “The most powerful
> set of tools available to create your Windows installation experience.”
>
> That makes more sense.
>
> Though it’s a shame that a multi-platform Java based installer could not
> be used (if such a thing exists).
>
>
>
> Merlin Beedell
>
> *From:* Keegan Witt 
> *Sent:* 11 February 2019 2:24 AM
> *To:* users@groovy.apache.org
> *Subject:* New Groovy Windows installer
>
>
>
> I'm working on a new installer <https://github.com/keeganwitt/groovy-wix>
> for Windows using WIX <http://wixtoolset.org/> to create an MSI
> installer, which should be more robust for things like altering environment
> variables and make it easier to do corporate installations.
>
>
>
> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure
> I've done some dumb things, but I hacked together a basic working installer
> this weekend.  I've put the initial version of the installer here
> <https://www.dropbox.com/sh/w2giakqb2jcc82e/AAB_gqvCvzOU1t-2dRlV4yBoa?dl=0>.
> Your feedback is appreciated.
>
>
>
> Some things I'm still thinking about or working on:
>
>- The start menu shortcuts for documentation don't go into a
>subfolder, I'm not sure why.
>- Heat will generate new GUIDs for the binaries and docs folders every
>time the project is built -- I'm not sure if that's the correct thing to 
> do.
>- Would you ever want to set GROOVY_HOME without adding to PATH?  Or
>add to PATH without setting GROOVY_HOME?  Currently the installer groups
>these together in a single feature.
>- We should use registry entries to remember which features the user
>selected to install, so those are automatically selected during upgrades.
>- Desktop shortcuts.
>- Quick launch shortcuts.  I don't think people use these much
>anymore, but I can throw them in -- maybe disabled by default?
>- Should I create an exe version of the installer as well as the msi?
>
> -Keegan
>

Re: Groovy file associations on Windows

[Keegan Witt]

Actually, for Gpars, that's in the Groovy binary zip, so that's
included already.

On Sun, Feb 17, 2019 at 6:42 PM Keegan Witt  wrote:
>
> I hear you.  But where do you draw the line?
>
> There are a lot of popular libraries we also could include besides Gpars and 
> Scriptom (e.g. Geb, Spock, groovy-wslite, http-builder-ng, Gru, gstorm, dru, 
> GroovyServ, Gaiden, shoogr, etc) -- and those are just some ones with commits 
> in the last year that aren't for building or hosting web stuff.  There are 
> many more besides this.  And because it's just a bundle including whatever 
> the latest versions were at the time of a Groovy release for a specific 
> selection of projects (and not a project like sdkman), there's no way to mix 
> & match versions or upgrade independent of a Groovy release.
> Although I guess if we want the installer to include a bunch of different 
> library options, maybe we could have the installer fetch the requested jars 
> from the internet, I suppose.  Though I'm not sure how the file GUIDs would 
> work if we did that.  MSIs I've seen that do that (like have .NET Framework 
> as a dependency) usually invoke a separate MSI for each dependency.
>
> -Keegan
>
>
> On Tue, Feb 12, 2019 at 2:13 AM Daniel Sun  wrote:
>>
>> Yep. e.g. banks usually does not allow employees access Internet. Luckily
>> some of them will setup maven server.
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: New Groovy Windows installer

[Keegan Witt]

And the Quick Launch toolbar was removed in Windows 7 (although it can
be added back manually), so I think I won't bother with those
shortcuts.  I never noticed it was removed because I never used it.

On Sun, Feb 17, 2019 at 6:56 PM Keegan Witt  wrote:
>
> Update: The documentation directory on the start menu actually does
> get created -- Windows 10 just doesn't show subdirectories on start
> menu folders like previous versions of Windows did.
>
> On Sun, Feb 10, 2019 at 11:07 PM Keegan Witt  wrote:
> >
> > Oh, and one important note for those playing with the new installer:
> > uninstall the NSIS based Groovy first and make sure GROOVY_HOME,
> > %PROGRAM_FILES%\Groovy, and PATH are free from references to the old
> > installation before proceeding.
> >
> > On Sun, Feb 10, 2019 at 9:26 PM Keegan Witt  wrote:
> > >
> > > Oh, one more item
> > >
> > > Is 200 the installer version I should use?
> > >
> > >
> > > On Sun, Feb 10, 2019 at 9:24 PM Keegan Witt  wrote:
> > >>
> > >> I'm working on a new installer for Windows using WIX to create an MSI 
> > >> installer, which should be more robust for things like altering 
> > >> environment variables and make it easier to do corporate installations.
> > >>
> > >> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure 
> > >> I've done some dumb things, but I hacked together a basic working 
> > >> installer this weekend.  I've put the initial version of the installer 
> > >> here.  Your feedback is appreciated.
> > >>
> > >> Some things I'm still thinking about or working on:
> > >>
> > >> The start menu shortcuts for documentation don't go into a subfolder, 
> > >> I'm not sure why.
> > >> Heat will generate new GUIDs for the binaries and docs folders every 
> > >> time the project is built -- I'm not sure if that's the correct thing to 
> > >> do.
> > >> Would you ever want to set GROOVY_HOME without adding to PATH?  Or add 
> > >> to PATH without setting GROOVY_HOME?  Currently the installer groups 
> > >> these together in a single feature.
> > >> We should use registry entries to remember which features the user 
> > >> selected to install, so those are automatically selected during upgrades.
> > >> Desktop shortcuts.
> > >> Quick launch shortcuts.  I don't think people use these much anymore, 
> > >> but I can throw them in -- maybe disabled by default?
> > >> Should I create an exe version of the installer as well as the msi?
> > >>
> > >> -Keegan

Re: New Groovy Windows installer

[Keegan Witt]

Update: The documentation directory on the start menu actually does
get created -- Windows 10 just doesn't show subdirectories on start
menu folders like previous versions of Windows did.

On Sun, Feb 10, 2019 at 11:07 PM Keegan Witt  wrote:
>
> Oh, and one important note for those playing with the new installer:
> uninstall the NSIS based Groovy first and make sure GROOVY_HOME,
> %PROGRAM_FILES%\Groovy, and PATH are free from references to the old
> installation before proceeding.
>
> On Sun, Feb 10, 2019 at 9:26 PM Keegan Witt  wrote:
> >
> > Oh, one more item
> >
> > Is 200 the installer version I should use?
> >
> >
> > On Sun, Feb 10, 2019 at 9:24 PM Keegan Witt  wrote:
> >>
> >> I'm working on a new installer for Windows using WIX to create an MSI 
> >> installer, which should be more robust for things like altering 
> >> environment variables and make it easier to do corporate installations.
> >>
> >> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure 
> >> I've done some dumb things, but I hacked together a basic working 
> >> installer this weekend.  I've put the initial version of the installer 
> >> here.  Your feedback is appreciated.
> >>
> >> Some things I'm still thinking about or working on:
> >>
> >> The start menu shortcuts for documentation don't go into a subfolder, I'm 
> >> not sure why.
> >> Heat will generate new GUIDs for the binaries and docs folders every time 
> >> the project is built -- I'm not sure if that's the correct thing to do.
> >> Would you ever want to set GROOVY_HOME without adding to PATH?  Or add to 
> >> PATH without setting GROOVY_HOME?  Currently the installer groups these 
> >> together in a single feature.
> >> We should use registry entries to remember which features the user 
> >> selected to install, so those are automatically selected during upgrades.
> >> Desktop shortcuts.
> >> Quick launch shortcuts.  I don't think people use these much anymore, but 
> >> I can throw them in -- maybe disabled by default?
> >> Should I create an exe version of the installer as well as the msi?
> >>
> >> -Keegan

Re: Groovy file associations on Windows

[Keegan Witt]

I hear you.  But where do you draw the line?

There are a lot of popular libraries we also could include besides Gpars
and Scriptom (e.g. Geb , Spock
, groovy-wslite
, http-builder-ng
, Gru
, gstorm
, dru ,
GroovyServ , Gaiden
, shoogr
, etc) -- and those are just some ones
with commits in the last year that aren't for building or hosting web
stuff.  There are many more besides this.  And because it's just a bundle
including whatever the latest versions were at the time of a Groovy release
for a specific selection of projects (and not a project like sdkman),
there's no way to mix & match versions or upgrade independent of a Groovy
release.
Although I guess if we want the installer to include a bunch of different
library options, maybe we could have the installer fetch the requested jars
from the internet, I suppose.  Though I'm not sure how the file GUIDs would
work if we did that.  MSIs I've seen that do that (like have .NET Framework
as a dependency) usually invoke a separate MSI for each dependency.

-Keegan


On Tue, Feb 12, 2019 at 2:13 AM Daniel Sun  wrote:

> Yep. e.g. banks usually does not allow employees access Internet. Luckily
> some of them will setup maven server.
>
> Cheers,
> Daniel.Sun
>
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
>

Re: Groovy file associations on Windows

[Keegan Witt]

Do folks using it really need it to be in the lib directory with all the
other jars? Or could they just use Grapes/Grab?

If it's truly helpful, I can keep it.  I'm just wondering if it's overkill.

On Mon, Feb 11, 2019, 2:19 AM Paul King  I'd be inclined to keep GPars in the mix for now. It isn't actively
> maintained but is still very useful in its current form and I hope to put
> some time into it at some stage.
>
> Cheers, Paul.
>
>
> On Mon, Feb 11, 2019 at 12:24 PM Keegan Witt  wrote:
>
>> In addition to removing projects that are no longer developed from the
>> Groovy Windows installer (Gpars, Gaelyk, Scriptom, EasyB, Gant, GMock), I'm
>> considering removing the exe files from groovy-native-launcher
>> <https://github.com/groovy/groovy-native-launcher>.  These haven't been
>> compiled in quite a while and are just another thing to maintain.  As I see
>> it, there are two primary benefits these provide.
>>
>>1. Provide a way to create file associations so you can double click
>>a Groovy file, or run myFile.groovy instead of groovy myFile.groovy.
>>2. Hide the command window when launching GroovyConsole.
>>
>> For #2, I can work around this with a VBScript file (or NirCmd).  #1
>> doesn't have a good way to solve other than the current native binary
>> solution since Launch4J doesn't support variable expansion
>> <https://sourceforge.net/p/launch4j/bugs/162/>.  My question is, do many
>> folks need this functionality?  It's something I've never personally used.
>> Please weigh in with your thoughts.
>>
>> -Keegan
>>
>

Re: New Groovy Windows installer

[Keegan Witt]

Oh, and one important note for those playing with the new installer:
uninstall the NSIS based Groovy first and make sure GROOVY_HOME,
%PROGRAM_FILES%\Groovy, and PATH are free from references to the old
installation before proceeding.

On Sun, Feb 10, 2019 at 9:26 PM Keegan Witt  wrote:
>
> Oh, one more item
>
> Is 200 the installer version I should use?
>
>
> On Sun, Feb 10, 2019 at 9:24 PM Keegan Witt  wrote:
>>
>> I'm working on a new installer for Windows using WIX to create an MSI 
>> installer, which should be more robust for things like altering environment 
>> variables and make it easier to do corporate installations.
>>
>> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure 
>> I've done some dumb things, but I hacked together a basic working installer 
>> this weekend.  I've put the initial version of the installer here.  Your 
>> feedback is appreciated.
>>
>> Some things I'm still thinking about or working on:
>>
>> The start menu shortcuts for documentation don't go into a subfolder, I'm 
>> not sure why.
>> Heat will generate new GUIDs for the binaries and docs folders every time 
>> the project is built -- I'm not sure if that's the correct thing to do.
>> Would you ever want to set GROOVY_HOME without adding to PATH?  Or add to 
>> PATH without setting GROOVY_HOME?  Currently the installer groups these 
>> together in a single feature.
>> We should use registry entries to remember which features the user selected 
>> to install, so those are automatically selected during upgrades.
>> Desktop shortcuts.
>> Quick launch shortcuts.  I don't think people use these much anymore, but I 
>> can throw them in -- maybe disabled by default?
>> Should I create an exe version of the installer as well as the msi?
>>
>> -Keegan

Re: New Groovy Windows installer

[Keegan Witt]

Oh, one more item

   - Is 200 the installer version I should use?


On Sun, Feb 10, 2019 at 9:24 PM Keegan Witt  wrote:

> I'm working on a new installer <https://github.com/keeganwitt/groovy-wix>
> for Windows using WIX <http://wixtoolset.org/> to create an MSI
> installer, which should be more robust for things like altering environment
> variables and make it easier to do corporate installations.
>
> I'm a total noob when it comes to Windows Installer and WIX, so I'm sure
> I've done some dumb things, but I hacked together a basic working installer
> this weekend.  I've put the initial version of the installer here
> <https://www.dropbox.com/sh/w2giakqb2jcc82e/AAB_gqvCvzOU1t-2dRlV4yBoa?dl=0>.
> Your feedback is appreciated.
>
> Some things I'm still thinking about or working on:
>
>- The start menu shortcuts for documentation don't go into a
>subfolder, I'm not sure why.
>- Heat will generate new GUIDs for the binaries and docs folders every
>time the project is built -- I'm not sure if that's the correct thing to 
> do.
>- Would you ever want to set GROOVY_HOME without adding to PATH?  Or
>add to PATH without setting GROOVY_HOME?  Currently the installer groups
>these together in a single feature.
>- We should use registry entries to remember which features the user
>selected to install, so those are automatically selected during upgrades.
>- Desktop shortcuts.
>- Quick launch shortcuts.  I don't think people use these much
>anymore, but I can throw them in -- maybe disabled by default?
>- Should I create an exe version of the installer as well as the msi?
>
> -Keegan
>

Groovy file associations on Windows

[Keegan Witt]

In addition to removing projects that are no longer developed from the
Groovy Windows installer (Gpars, Gaelyk, Scriptom, EasyB, Gant, GMock), I'm
considering removing the exe files from groovy-native-launcher
.  These haven't been
compiled in quite a while and are just another thing to maintain.  As I see
it, there are two primary benefits these provide.

   1. Provide a way to create file associations so you can double click a
   Groovy file, or run myFile.groovy instead of groovy myFile.groovy.
   2. Hide the command window when launching GroovyConsole.

For #2, I can work around this with a VBScript file (or NirCmd).  #1
doesn't have a good way to solve other than the current native binary
solution since Launch4J doesn't support variable expansion
.  My question is, do many
folks need this functionality?  It's something I've never personally used.
Please weigh in with your thoughts.

-Keegan

[ANNOUNCE] Groovy 2.5.6 Windows Installer Released

[Keegan Witt]

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

-Keegan

Groovy on ppc64le, arm64v8, and s390x

[Keegan Witt]

I'm trying to fix some errors I have in the Docker Groovy
 images on the ppc64le, arm64v8,
and s390x architectures. I don't personally have any experience working
with these architectures. Here are the errors I get

*powerpc64le
*
Dec 29, 2018 6:10:09 PM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [groovy-datetime] - Unable to load extension class
[org.apache.groovy.datetime.extensions.DateTimeExtensions]
Dec 29, 2018 6:10:09 PM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [groovy-datetime] - Unable to load extension class
[org.apache.groovy.datetime.extensions.DateTimeStaticExtensions]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:110)
at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128)
Caused by: java.lang.UnsatisfiedLinkError: Could not load library. Reasons:
[no jansi in java.library.path, /tmp/libjansi-64-6177151729256195035.so:
Error relocating /tmp/libjansi-64-6177151729256195035.so: unsupported
relocation type 7 (Possible cause: can't load AMD 64-bit .so on a Power PC
64-bit platform)]
at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
at org.fusesource.jansi.internal.CLibrary.(CLibrary.java:42)
at
org.fusesource.jansi.AnsiConsole.wrapOutputStream(AnsiConsole.java:48)
at org.fusesource.jansi.AnsiConsole.(AnsiConsole.java:38)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:195)
at
groovyjarjarpicocli.CommandLine$Help$Ansi.isJansiConsoleInstalled(CommandLine.java:9362)
at
groovyjarjarpicocli.CommandLine$Help$Ansi.ansiPossible(CommandLine.java:9358)
at
groovyjarjarpicocli.CommandLine$Help$Ansi.enabled(CommandLine.java:9376)
at
groovyjarjarpicocli.CommandLine$Help$Ansi$Text.toString(CommandLine.java:9728)
at java.lang.String.valueOf(String.java:2849)
at java.io.PrintStream.println(PrintStream.java:821)
at
groovyjarjarpicocli.CommandLine.printVersionHelp(CommandLine.java:1563)
at
groovyjarjarpicocli.CommandLine.printHelpIfRequested(CommandLine.java:1027)
at
groovyjarjarpicocli.CommandLine.printHelpIfRequested(CommandLine.java:995)
at groovy.ui.GroovyMain.processArgs(GroovyMain.java:130)
at groovy.ui.GroovyMain.main(GroovyMain.java:116)
... 6 more

*arm64v8
*
Dec 30, 2018 2:32:22 AM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [groovy-datetime] - Unable to load extension class
[org.apache.groovy.datetime.extensions.DateTimeExtensions]
Dec 30, 2018 2:32:23 AM
org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
WARNING: Module [groovy-datetime] - Unable to load extension class
[org.apache.groovy.datetime.extensions.DateTimeStaticExtensions]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java:110)
at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:128)
Caused by: java.lang.UnsatisfiedLinkError: Could not load library. Reasons:
[no jansi in java.library.path, /tmp/libjansi-64-6661390371961894243.so:
Error relocating /tmp/libjansi-64-6661390371961894243.so: unsupported
relocation type 7 (Possible cause: can't load AMD 64-bit .so on a
AARCH64-bit platform)]
at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
at org.fusesource.jansi.internal.CLibrary.(CLibrary.java:42)
at
org.fusesource.jansi.AnsiConsole.wrapOutputStream(AnsiConsole.java:48)
at org.fusesource.jansi.AnsiConsole.(AnsiConsole.java:38)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:195)
at
groovyjarjarpicocli.CommandLine$Help$Ansi.isJansiConsoleInstalled(CommandLine.java:9362)
at
groovyjarjarpicocli.CommandLine$Help$Ansi.ansiPossible(CommandLine.java:9358)
at

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

[Keegan Witt]

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
>>
>

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

[Keegan Witt]

 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

[ANNOUNCE] Groovy 2.5.5 Windows Installer Released

[Keegan Witt]

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

[ANNOUNCE] Groovy 2.4.16 Windows Installer Released

[Keegan Witt]

 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

[ANNOUNCE] Groovy 2.5.4 Windows Installer Released

[Keegan Witt]

 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: GMavenPlus 1.6.2 Released

[Keegan Witt]

Sorry, one point of clarification on a copy/paste error: the Java 10 and 11
bytecode changes are enhancements, not bugs.

On Sun, Oct 14, 2018 at 4:28 PM Keegan Witt  wrote:

> GMavenPlus 1.6.2 has been released to Sonatype OSS
> <https://oss.sonatype.org/content/repositories/public/> and should appear
> in Maven Central <http://search.maven.org/> shortly.
> Bugs
>
>- Support for Java 10 bytecode (#104
><https://github.com/groovy/GMavenPlus/issues/104>)
>- Support for Java 11 bytecode (#106
><https://github.com/groovy/GMavenPlus/issues/106>)
>- Fixed that could error saying no Groovy dependency when it shouldn't
>because no Groovy sources exist (ef3a3d5
>
> <https://github.com/groovy/GMavenPlus/commit/ef3a3d51dae4d13ab12821e679d594a8bf468179>
>).
>
> Enhancements
>
> None
> Potentially breaking changes
>
> None
> Notes
>
> None
>

[ANNOUNCE] Groovy 2.5.3 Windows Installer Released

[Keegan Witt]

 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
.

GMavenPlus 1.6.2 Released

[Keegan Witt]

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

[ANNOUNCE] Groovy 2.5.2 Windows Installer Released

[Keegan Witt]

 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
.

[ANNOUNCE] Groovy 2.5.1 Windows Installer Released

[Keegan Witt]

The Windows installer for Groovy 2.5.1 is available from the usual place:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.1-installer.exe
.

-Keegan

[ANNOUNCE] Groovy 3.0.0-alpha-3 Windows Installer Released

[Keegan Witt]

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

[ANNOUNCE] Groovy 2.6.0-alpha-4 Windows Installer Released

[Keegan Witt]

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

[ANNOUNCE] Groovy 2.5.0 Windows Installer Released

[Keegan Witt]

 The Windows installer for Groovy 2.5.0 is available from the usual place:
https://bintray.com/groovy/Distributions/download_file?file_path=groovy-2.5.0-installer.exe

-Keegan

[ANNOUNCE] Groovy 2.5.0-rc-3 Windows Installer Released

[Keegan Witt]

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

-Keegan

Re: Java survey, show your Groovy love ;-)

[Keegan Witt]

It's unfortunate it won't let you choose multiple primary application
languages, I think it's often an app is a mix of Java and Groovy.

On Fri, May 11, 2018 at 3:31 AM, Guillaume Laforge 
wrote:

> I just spotted this Java survey:
> https://snykteam.typeform.com/to/V4LOUZ
>
> They donate money to Devoxx4Kids if they have enough respondents.
>
> You can mention your preferred programming language (Groovy!), build tool
> (Gradle!), web framework (Grails!), testing tool (Spock!), code quality
> tool (Codenarc!), etc :-)
>
> In case you want to show your love ;-)
>
> Guillaume
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC Vice-President
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

GMavenPlus 1.6.1 Released

[Keegan Witt]

GMavenPlus 1.6.1 has been released to Sonatype OSS
 and should appear in
Maven Central  shortly.  Besides the usual minor
tweaks, this release includes

*Bugs*



[93 ] - Fixed that was
logging Groovy version as not supporting config script if config script
file didn't exist
[84 ] - Fixed NPE when
calling mojo without Groovy dependency
[NA] - Fixed that was logging compile classpath instead of test classpath
during test GroovyDoc generation

*Enhancements*

None

*Potentially breaking changes*

None
*Getting help / reporting bugs*

As usual, let me know of any bugs you encounter either on our user mailing
list (http://groups.google.com/group/gmavenplus), Github issues (
https://github.com/groovy/GMavenPlus/issues), or Slack (
https://groovy-community.slack.com/messages/C2SLAV9FY/).

Enjoy!