Update dependency org.codehaus.gmavenplus:gmavenplus-plugin to v1.13.1

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.codehaus.gmavenplus:gmavenplus-plugin (source)	1.9.0 -> 1.13.1

---

Release Notes

groovy/GMavenPlus

v1.13.1

Compare Source

Bugs

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

Enhancements

None

Potentially breaking changes

None.

Notes

None.

v1.13.0

Compare Source

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.

v1.12.1

Compare Source

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.

v1.12.0

Compare Source

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

This potentially runs slower than before, since a new classloader is instantiated each execution, rather than resuing the same classloader, so the classes referenced will have to be reinitialized.

v1.11.1

Compare Source

Bugs

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

Enhancements

None

Potentially breaking changes

None

Notes

None

v1.11.0

Compare Source

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

v1.10.1

Compare Source

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)

Potentially breaking changes

None

Notes

None

v1.10.0

Compare Source

Bugs

None

Enhancements

• Change default GroovyDoc jar artifact type to javadoc, so its extension gets set to "jar" by the artifact handler instead of "groovydoc" by the default handler logic which uses the type for the extension in the case of unknown types (#​151).

Potentially breaking changes

• GroovyDoc jars and test GroovyDoc jars will now be of type "javadoc" and have extension "jar".  Rather than type and extension "groovydoc".  If you do not wish to transition to this new behavior, set the new artifactType or testArtifactType property to "groovydoc" to revert to the previous behavior.

Notes

• While the artifact type of GroovyDoc jars has changed, the Maven classifier has not.  It remains "groovydoc", and you can still override that, just as before.

v1.9.1

Compare Source

Bugs

None

Enhancements

• Add a property to skip script execution (#​162)

Potentially breaking changes

None

Notes

None

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[renovate[bot]]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.