Bugs
- [38] - Compilation doesn't allow indy back far enough (thanks for pointing this out Pascal Schumacher!)
Enhancements
- [36] - Allow script files to be executed as filenames as well as URLs (see Significant changes of note for an example)
- [41] - Verify Groovy version supports target bytecode (See Potentially breaking changes for a description)
- [46] - Remove scriptExtensions config option
- [31/58] - Goals not consistantly named / IntelliJ improperly adding stub directories to sources
- [61] - You can now skip Groovydoc generation with new skipGroovyDoc property (Thanks rvenutolo!)
- [45] - GROOVY-7423 (JEP 118) Support (requires Groovy 2.5.0-alpha-1 or newer and enabled with new parameters boolean property)
Potentially breaking changes
- 46 will break your build if you are using . But the fix is simple, just the delete the configuration option and GMavenPlus will automatically do the right thing.
- 41 will break your build if you were passing an invalid target bytecode. GMavenPlus will no longer allow Groovy to silently default to 1.4 or 1.5. It will verify that the bytecode is supported by your Groovy version (that is, the option exists in org.codehaus.groovy.control.CompilerConfiguration), and fail if it isn't.
- 58 will require renaming goals testGenerateStubs to generateTestStubs and testCompile to compileTests. IntelliJ has hard-coded the goal names in their plugin, and these names will make IntelliJ work with both GMaven and GMavenPlus.
- In order to support using the latest Maven plugins (and to make GMavenPlus easier to maintain), GMavenPlus now requires Java 6 or newer and Maven 3.0.1 or newer (previously was Java 5 or newer and Maven 2.2.1 or newer).
- Due to an unintended side-effect of logging order change, adding a GMavenPlus goal without Groovy dependency will fail if there are no Groovy sources to use that goal with. If this is an issue for you, please let me know, and I'll consider reversing the order back.
testStubsOutputDirectoryandstubsOutputDirectoryinadvertently got renamed tooutputDirectory, which conflicts with the configuration in the compile and compileTests goals. You may need to setup separate executions with separate configurations for each if you need to set that configuration option.
Notes
- You can now use this syntax for executing scripts
<script>${project.basedir}/src/main/resources/groovyScripts/helloWorld.groovy</script>
in addition to the original style of
<script>file:///${project.basedir}/src/main/resources/groovyScripts/helloWorld.groovy</script> - This will be the last release that doesn't follow semantic versioning conventions.