Groovy
Groovy Closures: this, owner, delegate Let's Make a DSL
Closures are very powerful, they can delegate out to objects that can be set dynamically at runtime. That plays an important part in Groovy's meta programming capabilities which mean that Groovy can have some very expressive DSLs.
Sponsored Link
GR8Conf was started in 2009, thus making this edition the 10th. 🎂
Micronaut, Groovy, Grails, Spock, Geb, Gradle, devops...
Graeme Rocher, Paul King, Jeff Scott Brown, Marcin Erdmann, Schalk Cronjé, Marco Pas, Hubert Klein Ikkink...
This is the conference that you don't want to miss.
📍 IT-University of Copenhagen.
📅 May 30th to June 1st, 2018.
Apply this coupon code GR8CALAMARI20 at checkout to get a 20% off.
Micronaut
Today in London - Reactive Microservices with Micronaut & Open Cloud-Native Java
If you are in London, go to @alvaro_sanchez's presentation about Micronaut .
📍London.
📅 Today. 9th May, 18:00 – 21:00 at IBM UK, SE1 9PZ.
Grails
Introduction to Grails Security
Join me next week for an Online Workshop:
📍Online.
📅 May 17th and 18th.
⏳ 6 Hours (3 hours per day).
Understand the security capabilities of key Grails plugins
Learn to configure and use Grails security plugins (Spring Security Core, LDAP, REST, ACL, UI).
2018 - Grails Community Rock Star Award 🎸
Please help us choose 2018 Grails RockStar award by casting your vote in this link.
Do you need inspiration for a nominee? How about @daniel_sun. The guy has been a tremendous Groovy contributor in the past years. Grails no doubt benefit from Groovy contributors. Although sometimes opensource can be harsh, we appreciate his work a lot. Thanks, Daniel!
Tools
JFleet: persist to database large collections of Java POJO
JFleet is a Java library which persist in database large collections of Java POJOs as fast as possible, using the best available technique in each database provider, achieving it with alternate persistence methods from each JDBC driver implementation.
There is a nice introductory blog post by @jerolba in Spanish. Library docs are in English.
Misc
Trunk Based Development
When I first discovered git-flow, I thought: wow, it makes sense!. However, I came around to believe that for web applications, trunk base development is a better approach.
A source-control branching model, where developers collaborate on code in a single branch called ‘trunk’ *, resist any pressure to create other long-lived development branches by employing documented techniques. They therefore avoid merge hell, do not break the build, and live happily ever after.
Trunk-Based Development is a key enabler of Continuous Integration and by extension Continuous Delivery. When individuals on a team are committing their changes to the trunk multiple times a day it becomes easy to satisfy the core requirement of Continuous Integration that all team members commit to trunk at least once every 24 hours. This ensures the codebase is always releasable on demand and helps to make Continuous Delivery a reality.
There many events brewing in the community and this issue contains several links to those so that you don't miss any.
Moreover, there are a couple of juicy links (Trunk Based Development, JFleet) outside the Groovy Ecosystem which I hope you find interesting.
Sergio del Amo