groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: GMavenPlus 1.6 Released
Date Tue, 12 Sep 2017 05:58:23 GMT
Nice work!

On Tue, Sep 12, 2017 at 2:06 PM, Keegan Witt <keeganwitt@gmail.com> wrote:

> GMavenPlus 1.6 has been released to Sonatype OSS
> <https://oss.sonatype.org/content/repositories/public/> and should appear
> in Maven Central <http://search.maven.org/> shortly.  Besides the usual
> minor tweaks, this release
> <https://github.com/groovy/GMavenPlus/issues?q=milestone%3A1.6> includes
>
> *Bugs*
> [38 <https://github.com/groovy/GMavenPlus/issues/38>] - Compilation
> doesn't allow indy back far enough (thanks for pointing this out Pascal
> Schumacher!)
>
>
> *Enhancements*
> [36 <https://github.com/groovy/GMavenPlus/issues/36>] - Allow script
> files to be executed as filenames as well as URLs (see Significant changes
> of note for an example)
>
> [41 <https://github.com/groovy/GMavenPlus/issues/41>] - Verify Groovy
> version supports target bytecode (See Potentially breaking changes for a
> description)
>
> [46 <https://github.com/groovy/GMavenPlus/issues/46>] - Remove
> scriptExtensions config option
>
> [58 <https://github.com/groovy/GMavenPlus/issues/58>] - IntelliJ
> improperly adding stub directories to sources
>
> [61 <https://github.com/groovy/GMavenPlus/pull/61>] - You can now skip
> Groovydoc generation with new skipGroovyDoc property (Thanks rvenutolo
> <https://github.com/rvenutolo>!)
>
> [45 <https://github.com/groovy/GMavenPlus/issues/45>] - GROOVY-7423 (JEP
> 118 <http://openjdk.java.net/jeps/118>) Support (requires Groovy
> 2.5.0-alpha-1 or newer and enabled with new parameters boolean property)
>
> *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.CompilerConfiguration),
> and fail if it isn't.
>
> 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
>
> <script>${project.basedir}/src/main/resources/groovyScripts/helloWorld.
> groovy</script>
>
> in addition to the original style of
>
> <script>file:///${project.basedir}/src/main/resources/groovy
> Scripts/helloWorld.groovy</script>
>
> *Getting help / reporting bugs*
>
> As usual, let me know of any bugs you encounter either on our user mailing
> list (http://groups.google.com/group/gmavenplus), Github issues (
> https://github.com/groovy/GMavenPlus/issues), or Slack (
> https://groovy-community.slack.com/messages/C2SLAV9FY/).
>
> Enjoy!
>
> -Keegan
>

Mime
View raw message