Update dependency org.codehaus.gmavenplus:gmavenplus-plugin to v1.13.1 #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.6→1.13.1Release Notes
groovy/GMavenPlus (org.codehaus.gmavenplus:gmavenplus-plugin)
v1.13.1Compare Source
Bugs
bindAllProjectPropertiesandbindSessionUserOverridePropertiestogether can cause an NPE (thanks for reporting this @sebthom!).Enhancements
None
Potentially breaking changes
None.
Notes
None.
v1.13.0Compare Source
Bugs
None.
Enhancements
Potentially breaking changes
None.
Notes
None.
v1.12.1Compare Source
Bugs
Enhancements
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.0Compare Source
Bugs
PROJECT_ONLYclasspath. Thanks for reporting this @TobiX!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.1Compare Source
Bugs
consoleScriptparameter was loaded from POM rather than command line property.Enhancements
None
Potentially breaking changes
None
Notes
None
v1.11.0Compare Source
Bugs
None
Enhancements
attachGroovyDocAnnotation) to enable attaching GroovyDoc annotation.parallelParsing) to enable parallel parsing (enabled by default with Groovy 4).previewFeaturesparameter from stub generation goals, since it's not used there.Potentially breaking changes
previewFeaturesparameter 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.1Compare Source
Bugs
None
Enhancements
Potentially breaking changes
None
Notes
None
v1.10.0Compare Source
Bugs
None
Enhancements
Potentially breaking changes
artifactTypeortestArtifactTypeproperty to "groovydoc" to revert to the previous behavior.Notes
v1.9.1Compare Source
Bugs
None
Enhancements
Potentially breaking changes
None
Notes
None
v1.9.0Compare Source
Bugs
None
Enhancements
skipBytecodeCheckproperty 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.Potentially breaking changes
maven.groovydoc.skipproperty was renamed toskipGroovydocso it matches the pattern of the other properties and won't seem to imply it's a property for a standard Maven plugin.Notes
v1.8.1Compare Source
Bugs
HashSettoTreeSet, to avoid unpredictable Groovy compiler output on certain filesystems (thanks @marcphilipp!).Enhancements
None
Potentially breaking changes
System.exits to allowing them.Notes
None
v1.8.0Compare Source
Bugs
Enhancements
<includeClasspath>PLUGIN_ONLY</includeClasspath>.Potentially breaking changes
#140
If you were using
useSharedClasspathbefore, you will need to replace it with new values. In most cases, this would beAnother 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
v1.7.1Compare Source
Bugs
Enhancements
Potentially breaking changes
None
Notes
None
v1.7.0Compare Source
Bugs
Enhancements
Potentially breaking changes
#120 corrects an inadvertent breaking change made in 1.6.0 with #31/#58. Here are those changes:
In addition, unused parameters have been removed:
addSources
addStubSources
addTestSources
addTestStubSources
compile
compileTests
console
execute
generateStubs
generateTestStubs
groovydoc
groovydocTests
removeStubs
removeTestStubs
shell
Lastly,
addTestStubSourcesandremoveTestStubsnow respect theskipTestsflag, for consistency.Notes
None
v1.6.3Compare Source
Bugs
None
Enhancements
Potentially breaking changes
None
Notes
None
v1.6.2Compare Source
Bugs
ef3a3d5).Enhancements
Potentially breaking changes
None
Notes
None
v1.6.1Compare Source
Bugs
Enhancements
None
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.
This PR was generated by Mend Renovate. View the repository job log.