The past few weeks, the Groovy team has been working on a new website for the project.

Without further ado, let me introduce you to its beta: http://beta.groovy-lang.org.

The website is actually a Groovy and Gradle application that you can fork and help us improve! So don’t hesitate to contribute fixes for things like typos or broken English, or suggest new relevant sections, etc. Your help will be welcome. Notice the “improve this doc” buttons on all pages which lead you to the relevant Github page that you can edit live, inline, on Github (if you’ve got an account already).

A big week for the Gradle team as they’ve just announced the final release of Gradle 2.0! It’s of course a very important milestone for the project, and it’s nice to see that the migration to Groovy 2.3 as a baseline.

There are also some updates to Grails, Ratpack, and also the launch of the Spring IO platform that you might be interested in.

You’ll see also a list of job postings for Netflix, where Groovy is deployed at a very large scale and who are always seeking Groovy talents.

This week, I’d like to highlight how you can contribute to the Groovy project!

The Groovy core team is a very small team, compared to the huge team a company like Oracle puts behind Java and the JVM, or Microsoft behind its languages and the .Net platform. So all contributions, in any form, count, and are important to the success and evolution of the Groovy language.

If you want to contribute to the code of Groovy, Cédric Champeau recorded a screencast showing how you can set up IntelliJ IDEA to be able to work on the Groovy codebase.

Oracle is publishing the agenda of the upcoming JavaOne 2014 conference. And I’d like to highlight the Groovy presentations I’ve noticed that you might be attending in following if you are in San Francisco:

• Groovy in the Light of Java 8 [CON5839] With Java 8 out the door, Java developers can at last benefit from the long-awaited lambdas to taste the newly found functional flavor of the language. Streams are there to work more easily and efficiently with heaps of data. Those things are not new to developers acquainted with Groovy. But what is left to Groovy to make it attractive beyond all the aspects in which Java has caught up with Groovy? In this session, a Groovy project lead shows you how Groovy is still relevant in the JVM landscape, how similar or different Java and Groovy can be, how Groovy further improves the developer experience on top of JDK 8, and what Groovy offers beyond Java.
• Groovy in 2014 and Beyond [CON5996] With three million downloads in a year, Groovy still clearly leads the pack of alternative languages on the JVM, but it’s not resting on its laurels. The latest Groovy release, 2.3, is chock-full of useful new features and performance improvements. In particular, Groovy now supports the concept of “traits” for elegantly composing behaviors. Its JSON support is now the most performant of all the JSON libraries available to date. Groovy 2.3 introduces a new markup-based template engine, new code transformations, and much more. In this session, a Groovy project lead guides you through the latest advancements in the Groovy programming language and tells you what’s cooking for the next releases.
• Exploring Groovy Metaprogramming [CON1768] One of the key benefits of Groovy is its metaprogramming capability. The built-in features of the language enable you to realize AOP without the need for any heavyweight tools. This presentation takes an in-depth look at the metaprogramming capabilities of Groovy and explains when to use mixins, method injection, and method synthesis.
• Functional Programmning the Groovy Way [CON3538] In recent years, functional programming has gained ground over object-oriented programming, mainly due to the advancement in computing power. The JVM is no exception. You can find powerful contenders in Clojure and Scala, but Groovy is not that far back in the race. The Groovy programming language contains a wide array of APIs and features that facilitate a functional programming style, such as closure composition, memorization, trampolines, and iterator methods. This session explores all of these features that are sure to spice up your daily experience.
• Rethinking API Design with Groovy Traits [CON2425] Groovy 2.3 introduces the concept of traits in the language. Traits look like interfaces but enable the developer to add both implementation and state. They introduce multiple inheritance in the language while avoiding the diamond problem. Traits will let you rethink the way you design APIs in Groovy, by favoring composition of behaviors. This session explains what traits are, how they were implemented in Groovy, and what they have to offer to make your code more readable and maintainable.
• Groovy and Grails Puzzlers: As Usual—Traps, Pitfalls, and End Cases [CON1764] Remember the epic Java puzzlers? Here’s the Groovy version, and there are some neat ones! Even though it is totally a Grails shop, some of these had JFrog people scratching their head for days, trying to figure them out. And there is more! Contributions from the truly Groovy senseis, including @glaforge, @aalmiray, @tim_yates, and @kenkousen, make this session an unforgettable journey to Groovy’s O_O. You’ll get the expected dose of fun and enlightenment while hearing about mistakes and failures, great and small, in hard-core Groovy/Grails development.
• Applying Groovy Closures for Fun and Productivity [CON1769] You can program higher-order functions in Groovy quite easily by using closures, but the benefits of closures go far beyond that. Groovy has a variety of capabilities hidden in closures. This presentation unlocks that treasure and explores ways in which we can design applications by using Groovy closures to apply different design patterns, to create fluent interfaces, and even to program asynchrony.
• HTML5/AngularJS/Groovy/Java and MongoDB Together: What Could Possibly Go Wrong? [CON1703] We hear it’s common to create a minimum viable product (MVP) in a language that facilitates rapid prototyping and then migrate to the JVM when the application requires better stability and performance. In this session, the speaker uses Java to create a web application in less than hour. The JVM is a polyglot platform, and you’ll learn how to use the correct tools for this application, including AngularJS, Bootstrap, HTML5, web services, Java, MongoDB, and Groovy—it’s fully buzzword-compliant. The presentation doesn’t go into every technology in depth but demonstrates the role of each tool and how the tools interact. The session will result in a fully working mobile/browser-friendly app without compromise of design or good practice. It’s even going to have tests.
• Plugging Users In: Extend Your Application with Pluggable Groovy DSL [CON1752] It is often beneficial to enable users to extend your software with their own logic, and with dynamic languages on the JVM, it is also easy to do so. This session shares JFrog’s experience in creating a public, Groovy-authored user plug-in interface. It explains what domain-specific languages (DSLs) are, what their relevance to user plug-ins is, and how they can be implemented in Groovy or Java. It also discusses another very important aspect of pluggability: good public API design. Further, it covers security concerns and how they should be tackled. And finally, it discusses classpath isolation issues you may run into and compares different solutions to this problem.
• Script Bowl 2014: The Battle Rages On [CON2939] In this contest, languages that run on the JVM, represented by their respective language nerds, battle for bragging rights as the most popular language by showing off their shiny new features. Adding a twist to the format in which the audience members will pick this year’s winner(s): they will also vote on a language that should not return in 2015. Returning from 2013 are language gurus representing Clojure, Groovy, JRuby, and Scala. Attend this fun-filled and technically invigorating session to judge which scripting language best meets your needs. You’ll also be able to compare the respective languages and spark some thought-provoking discussions with the panelists that will be beneficial to the entire Java community.
• Spring 4TW! [CON3693] Spring 4’s here, and with it comes a bevy of new features designed to support modern web developers as well as enrich the component model and enable even-more-adaptive enterprise applications. Spring 4 also serves as the underpinning of Spring Boot, the entry point into the Spring platform. In this session, a Spring developer advocate discusses Spring 4’s new support for WebSocket (including extra support for STOMP), conditional configuration, dependency injection, Java 8 and Java EE 7 support (JCache support, the Batch JSR, ManagedExecutorService support, and so on), the Groovy language, and more. The presentation also looks at Spring Boot as a productive entry point into the Spring platform.
• Writing Highly Concurrent Polyglot Applications with Vert.x [CON7902] Vert.x is a lightweight, high-performance, polyglot, asynchronous application platform for the JVM. This session covers the design principles and motivation behind Vert.x, including its concurrency model, and discusses why Vert.x is a great fit for super-simple, highly concurrent applications. It also dives into some of the key Vert.x features, including the distributed event bus and high availability, and discusses some of the up-and-coming new features in the latest development branch for Vert.x 3.0, including distributed map support, management, and monitoring. The presentation includes demonstrations involving examples in several JVM languages such as Java, JavaScript, Scala, and Groovy.

Update: I only searched sessions with the “groovy” keyword, but other Groovy ecosystem projects are also present, like Griffon, Gradle or Spock! So let me fix that by appending some more Groovy-related sessions to my list!

So what’s new this week?

We can highlight the first beta of Groovy 2.4 with the Android support, so users can start having a go at writing Android applications in Groovy! As well as bug fixes releases for Grails 2.3.x and 2.4.x.

Let’s also mention the launch of the Gradle plugin portal, announced last week at the Gradle Summit. And you’ll find also lots of presentations from the conference.

Releases

• Groovy 2.3.3 released and Groovy 2.4.0-beta-1 with Android support is out too
• Grails 2.4.1 and 2.3.10 released with loads of bug fixes
• Spring Boot 1.1 released
• Spring Boot 1.1.1 is out, fixing a little issue with the 1.1.0 release
• Marcin Erdmann announces the release of Geb 0.9.3
• Gretty 0.0.24 is out, with full support of Spring Boot 1.1.0
• Redis GORM 1.0.0 released
• Cédric Champeau released a JMH Gradle Plugin that integrates the JMH micro-benchmarking framework with your Gradle build

Articles

• Marc Palmer on the journey from Objective-C to Groovy
• MrHaki’s Getting Groovy extensive tutorial
• MrHaki’s Spock-light: on using an extra data variable for unroll description, based on Rob Fletcher’s GR8Conf Europe Spock talk
• Graeme Rocher blogs about a Gradle to get the nice GroovyDoc style from Groovy 2.3+ even if your project is using Groovy 2.2 or below
• Docker containers with Gradle in 4 easy steps, by Andy Glover
• Andrés Almiray wrote about the Griffon 2.0.0 beta
• Pooling web service connections in Grails by Jeff Sheets
• Building enterprise Mule applications with Gradle: part 1, part 2, part 3

Presentations from the Gradle Summit

• Justin Ryan from Netflix on the Nebula Gradle plugin, a useful test harness for Gradle plugins
• David Carr on cloud browser testing with Gradle and Geb
• Benjamin Muschko on web application deployments with Gradle
• Benjamin Muschko on provisioning virtualized infrastructure with Gradle
• Tobias Gesellchen shares his slides and code snippets on moving from Maven to Gradle
• Rene Gröschke on releasing with Gradle
• Dan Woods spoke about his Gradle provisioning plugin
• Andrés Almiray was spreading the word about Groovy, Gradle, Spock and more in Mexico (Spanish content)

News

• Gradleware just announced the launch of the Gradle plugin portal
• Guillaume Laforge shares the future look of the new Groovy documentation
• Jacobe Aae Mikkelsen on the Grails Diary week 24
• Learn about the GrooScript roadmap

Mailing-list posts

• An interesting thread on selling Groovy to your management
• A “provided scope” might come to Gradle

Code snippets

• An intentionally vulnerable Grails application for education purpose
• A demo project show-casing the Gradle tooling API

Contributions

• Grant McConnaughey contributed documentation on Groovy “statements”. Thank you, Grant. To all, please don’t hesitate to help us and contribute to the documentation effort!

Tweets

• A good way to get started with Groovy, with the GroovyKoans
• The Estonian emergency system is powered by Grails and Atmosphere
• Gradle 2.0 is 20% to 70% more performant than Gradle 1.0
• The Gradle plugin portal is built with Ratpack and RxJava
• You can start submitting your Gradle plugin to the Gradle plugin portal
• Cédric Champeau announces his JMH Gradle plugin and showing a sample project using it
• Andrés Almiray things the Gradle plugin portal has been rushed a bit, in time for Gradle Summit, as it’s still a bit complicated to submit plugins for inclusion
• Cédric Champeau notices only minor changes are needed to be able to build Groovy with Gradle 2.0-rc-1
• Initial work from Russell Hart bringing Ratpack into the “Reactive Streams” family
• Cédric Champeau would like to see the “new” keyword totally optional in Groovy, without using @Newify
• Guillaume Laforge suggests creating an “Enterprise” version of Groovy’s “spaceshift” operator
• Magnus Rundberget explores the Ratpack Gradle dependencies with the LightTable Groovy plugin 0.0.6
• The Grails GORM groovydoc is available standalone
• Cédric Champeau is surprised when people say using “def” makes a dynamic type (but “def” == “Object”)
• Cédric Champeau remarks that Groovy is a strongly typed language
• CRaSH 1.3.0 is available in GVM
• CrudZilla’s HiveMind web app generator is written largely in Groovy through JSR-223
• The Gradle Node plugin gives you an easy way to install and run Node.JS on Continuous Integration environments
• Burt Beckwith is going to each Groovy and Grails again at Harvard

Jobs

• A Groovy / Grails developer for Plano in Texas, USA

Events

• Cédric Champeau will speak about Groovy Traits at JavaOne
• JavaOne session acceptance emails are starting to flow, and the first Groovy sessions are appearing, for instance Guillaume Laforge’s on the latest & greatest Groovy, or Groovy in the light of Java 8
• MrHaki’s report on GR8Conf Europe 2014
• Quick summary from Andrés Almiray about the GR8Conf Europe 2014 Hackergarten

The Groovy team is very happy to announce the joint releases of Groovy 2.3.3 and Groovy 2.4-beta-1.

Groovy 2.3.3 is a bug fix release, particularly covering the recent issues discovered around anonymous inner classes. Please upgrade to 2.3.3 if you’ve been facing such issues.

Groovy 2.4.0-beta-1 comes pretty early, as we would like to come back to releasing milestones on a more regular pace, compared with how late we released the first beta of Groovy 2.3. We really want you, our users, to be able to give us feedback as soon as possible!

GR8Conf Europe is over, but there’s a lot to learn from the conference, with all the interesting conference sessions that took place there in Copenhagen.

The themes for this week will be around GR8Conf, of course, but also about Groovy on Android, again the Swift language, and also the first impressive demo of Grails 3.0!

Right after the conference also took place the annual Groovy DevCon meetup, gathering core members of the Groovy team, Grails team, and members of the Groovy ecosystem. Lots of interesting tidbits about what’s coming up in Groovy!

Direct live from GR8Conf Europe!

Several speakers already uploaded their presentation slides, as you shall see in the “presentations” sections. And the videos will be available later after the conference.

At the same time in San Francisco, Apple is running its WWDC conference and announced the creation of a new language, Swift, that looks a lot like Groovy as several Groovy users have already noticed on Twitter. That’s nice to see Groovy also influences other languages!

During Apple’s WWDC conference was announced a new programming language, called Swift, targeted at developing on iOS devices (and likely Mac OS X in the future as well).

When looking through the slides from the keynote, online documentation, and iTunes ebook, an acquainted Groovy eye would immediately notice the inspiration the Swift designers took from Groovy.

In one of the slides covering Swift, Groovy was even mentioned as one of the languages clearly making developers much more productive, although I disagree with the placement of Groovy in terms of performance as Groovy should clearly be leading the pack of the bottom right hand quadrant.

The Groovy team is pleased to announce the release of Groovy 2.3.2, a bug fix release for our 2.3 main branch.

If you have already moved to Groovy 2.3, we strongly recommend you to upgrade to 2.3.2 rapidly, as our two prior 2.3 releases were using a buggy version of ASM which was generating wrong bytecode for inner classes.

You can check this issue for more details: https://jira.codehaus.org/browse/GROOVY-6808

Since any code compiled with Groovy 2.3.0 or 2.3.1 and using inner classes is likely to have faulty bytecode, please make sure to recompile everything with 2.3.2
Our detailed JIRA change log: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10242&version=20402