- Verify Groovy version supports target bytecode (See Potentially breaking changes for a description)
 - Remove scriptExtensions config option
 - IntelliJ improperly adding stub directories to sources
Potentially breaking changes
Issues 46 will break your build if you are using <scriptExtensions>. But the fix is simple, just the delete the configuration option and GMavenPlus will automatically do the right thing.
Issue 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.
Issue 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).
Significant changes of note
You can now use this syntax for executing scripts
in addition to the original style of
Getting help / reporting bugs
As usual, let me know of any bugs you encounter either on our user mailing list (http://groups.google.com/grou
On Tue, Sep 12, 2017 at 2:06 PM, Keegan Witt <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|