Skip to content

Releases: groovy/GMavenPlus

4.3.1

12 Feb 05:56

Choose a tag to compare

Bugs

  • Fixed an issue where the compile goal would fail when there were no Groovy sources to compile (#358).

Enhancements

None

Potentially breaking changes

None

Notes

Full Changelog: 4.3.0...4.3.1

4.3.0

21 Jan 21:53

Choose a tag to compare

Bugs

Enhancements

  • Support toolchains for compilation, GroovyDoc, and stub generation (#349 and #356). You can also opt-in to using a forked process using the new fork parameter.

Potentially breaking changes

None

Notes

Full Changelog: 4.2.1...4.3.0

4.2.1

04 Jul 02:08

Choose a tag to compare

Bugs

  • Fix compatibility with Groovy 4.0.27 and 5.0.0-beta-1 which changed (GROOVY-11668) the signature of the GroovyDocTool constructor (#335).

Enhancements

None.

Potentially breaking changes

None.

Notes

None.

4.2.0

28 Apr 02:16

Choose a tag to compare

Bugs

None

Enhancements

  • Support Java 24 and 25 (#330)
  • Support Maven 4 (#328) Thanks to @gnodet for this PR!

Potentially breaking changes

None

Notes

None

4.1.1

02 Jan 23:12

Choose a tag to compare

Bugs

  • Accidentally changed required Maven version from >=3.6.3 to >=3.9.9 (#324).

Enhancements

None

Potentially breaking changes

None

Notes

None

4.1.0

01 Jan 15:47

Choose a tag to compare

Bugs

None

Enhancements

  • Add a property for scripts parameter, so it can be specified from the command line (#316).
  • Add timeouts for connecting and reading from scripts URLs (#317).

Potentially breaking changes

None

Notes

None

4.0.1

02 Oct 18:21

Choose a tag to compare

Bugs

  • Fix broken plugin due to problems encountered during release process (#314)

Enhancements

None

Potentially breaking changes

None

Notes

None

4.0.0

02 Oct 13:33

Choose a tag to compare

Bugs

None

Enhancements

  • Support Java 22 and 23 (#302)
  • Multiple dependency upgrades, including some that fixed CVEs
  • Added a warning about using SecurityManager to prevent System.exit() calls. JEP 411 deprecated SecurityManager in Java 17, for future removal. It is unclear what it will be replaced with for the use case of preventing System.exit() usages. JDK-8199704 is one possibility.

Potentially breaking changes

  • Updated the required Maven version to 3.6.3 to conform to the compatibility plan (#309)

Notes

None

3.0.2

28 Sep 20:57

Choose a tag to compare

Bugs

[#280] The 3.0.1 jar was corrupt (thanks @eugene-sadovsky for reporting this!).

Enhancements

Potentially breaking changes

None.

Notes

The CVE 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.

3.0.1

28 Sep 16:53

Choose a tag to compare

Bugs

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

Enhancements

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.