Last week, Codehaus has gone the way of the dodo. The lights are switching off. A page is turning.

So please remember about our infrastructure changes, as we move the Groovy project through the incubation process at Apache: the JIRA issue tracker has moved, and don’t forget that the Groovy mailing-lists are also moving. The Apache Git repository is now the new mainline, but you can contribute pull requests on the new Apache Groovy Github mirror. Be sure to update all your bookmarks, and register on the new mailing-list!

Groovy Weekly skipped a beat as I was very busy: I was very fortunate to spend my last week in California for various meetings, plus being a keynote speaker at JFrog’s SwampUp conference in Napa Valley. I had the chance to speak again about the Groovy release process and its history (based on my recent Devoxx talk).

Congrats to the Gradle team for releasing Gradle 2.4 with much faster builds!

Hurry up to register to GR8Conf Europe 2015, as registration closes on May 15th! Hurry up, and join the Groovy ecosystem fans gathering!

Remember the Android support of Groovy 2.4? Well, the new New York Times Android application, written in Groovy and using RxJava is now live! If a hugely popular Android app is leveraging Groovy, yours can too!

With Groovy’s move to the Apache Software Foundation, don’t forget to star the new Groovy Github repository!

Don’t miss the interesting interviews of Jeff Brown and Guillaume Laforge.

Reminder about our infrastructure changes, as we move the Groovy project through the incubation process at Apache: the JIRA issue tracker has moved, and don’t forget that the Groovy mailing-lists are also moving. The novelty this week is that the Apache Git repository is now the new mainline, but you can contribute pull requests on the Apache Groovy Github mirror.

No big focus this week in the editorial, but as in the previous edition, I’d like to remind you about the following infrastructure changes, as we move the Groovy project through the incubation process at Apache: the JIRA issue tracker has moved, and don’t forget that the Groovy mailing-lists are also moving. The novelty this week is that the Apache Git repository is now the new mainline, but you can contribute pull requests on the Apache Groovy Github mirror.

We’re only mid April but what a year it’s been so far! From Groovy & Grails’ loss of funding, leading Grails to a new home at Object Computing Inc. and Groovy at the Apache Software Foundation, to Guillaume Laforge joining Restlet and Cédric joining GradleWare. Against all odds, Groovy released its 2.4 version with the Android support, and the big 3.0 release of Grails saw the light of day. And on another personal note… I’ve finished my first marathon! What’s next for the rest of the year?

I hope you all had a Groovy Easter, with baskets full of eggs and chocolate!

Little update on the Groovy infrastructure, as the project moves into incubation at Apache, the JIRA issue tracker has moved, and don’t forget that the Groovy mailing-lists are also moving.

Releases

• SwissKnife 1.2.3 released, the Swiss knife for for Android development with Groovy
• Ratpack 0.9.15 released
• Spock Subjects Collaborators Extension 1.0.3 released by Marcin Grzejszczak
• Grails 3.0.1 released
• ElasticSearch Groovy client v1.5.0 released

Articles

• Grails 3.0 built upon Spring Boot and Gradle on JaxEnter
• Using Android product flavors to build full and demo version of an application, by Manij Shrestha

News

• The Groovy JIRA has now moved to Apache
• Gradle has a brand new forum powered by Discourse
• Tim Fox shares a glimpse of the upcoming new Vert.x website
• Jacob Aae Mikkelsen Grails Diary week 14

Presentations

• SpringOne2GX 2014
  • Ratpack and Grails 3 by Lari Hotari
  • Building awesome APIs with Grails by Chris Latimer
  • Gradle for Android by Ken Kousen
  • Introduction to Grails 3.0 by Dan Vega
  • Creating and running a Grails 3 application by Dan Vega

Tweets

• Creating iOS applications with Groovy and GrooScript, using ReactJS native
• April Fools from Apache Groovy mentor says Groovy could graduate on April 1st already
• Spring Boot 1.1.12 available on GVM
• Spring Boot 1.2.3 available on GVM
• Grails 3.0.1 available on GVM

Mailing-list posts

• Groovy’s JIRA moved to Apache

Books

• Peter Ledbrook shares early draft chapters of his Practical Groovy self-published book

Events

• GR8Conf US 2015 registration is open

Today marks the end of the sponsorship of the Groovy and Grails projects by Pivotal. The projects are now turning a new page in their lives. For Groovy, the project is going to wear some feathers, with joining the Apache Software Foundation. And Grails is releasing its major 3.0 version.

With Groovy’s move to Apache, it’s important to notice that the Groovy mailing-lists are moving. You must subscribe to the new mailing-lists at Apache, as we won’t force-subscribe people, so you’ll have to opt-in to these new lists.

The big news today is that Groovy has now passed the vote for entering the Apache Software Foundation incubator! Thus, in the coming weeks and months, while going through the incubation process, you can expect some changes in terms of infrastructure (moving sources, issue tracker, mailng-lists, etc) to be taking place, but don’t worry, we’ll keep you informed along the way.

This past week, we’ve had some new releases of Groovy, as well as the second release candidate for Grails 3! Grails 3 is really really close now, get ready, it’s gonna rock the house!

The Groovy team is happy to announce another 2.4 release, with Groovy 2.4.3.

We noticed some regressions that needed our attention, and we decided to release rapidly after our recent 2.4.2 release of last week. Please upgrade to 2.4.3 if you’re on the 2.4.x line.

You can read about the tickets resolved in our changelog: http://groovy-lang.org/changelogs/changelog-2.4.3.html

And you can download the Groovy distribution as usual on the new Groovy website.

I’d also like to announce that Groovy passed the vote to enter the Apache Software Foundation Incubator! In the coming weeks, we’ll be through the incubation process, likely for a few months, where we’ll be moving things around (sources, JIRA, mailing-lists, etc), so you can expect a bit of change, but we’ll keep you posted on how we progress along.

The Groovy development team is happy to announce the bug fix releases of Groovy 2.4.2 and Groovy 2.3.11.

For the 2.4.2 release, some key performance improvements have found their way in static compilation mode, so you might be happy to see your programs snappier!

Along with those two releases, you’ll notice lots more documentation has been written on the new Groovy website, as well as important updates to existing topics. You might want to have a look at the following new or improved sections: