Monthly Archives: October 2011

Grails quick tip: Testing Spock Interactions wrapped by the Executor plugin

We ran into an interesting issue today working with Spock, Grails and the executor plugin.

The executor plugin allows you to move tasks that might be long running into the background of your application.

In this post, I will show you how to unit test spock interactions wrapped inside the runAsync methods provided by the plugin.
Continue reading

Advertisements

Six ways to become a better Grails programmer

1. Read the Groovy books

Groovy is the heart of Grails, but it is surprising how easy it is to get by writing code the Java way.

I think it was four months after I started writing code in Grails that I started looking at the Groovy books, and they definitively helped me improve the code I was writing tremendously.

Continue reading

Migrating from the Grails UI-performance plugin to resources plugin.

The UI-performance plugin has been a standard for managing images, css and javascript files for many grails applications. In the upcoming Grails 2.0 release, however, it seems that the recommended way of managing resources is via the Resources plugin.

Many of the posts on the web ( like this one, or this one )describe how to get started with the Resources plugin from scratch. However, chances are that your project already uses UI-performance. How easy is it to migrate an existing project to use Resources?

In this post, I would like to document the steps we took to migrate our Grails project from the UI-performance plugin to the new resources plugin.
Continue reading

Job specs that make your team shine – building a spec with your development team

Secret Escapes is a great place to work for. Our team is multi-cultural and fun, we use the latest tools in the Grails ecosystem, and we work very well together.

However, I always found it difficult to present this to job applicants. Our initial job postings where hastily copied from other job postings and failed to present our culture of sharing and collaboration.

We recently had an opening for a Junior Grails Developer, and I thought it would be interesting to have the team help me come up with a new job spec that would reflect the company they would be working with.

After a couple of hours, we came up with a new job description that we think presented our development team much better.

In the old spec, we focused a lot on the technology side of things. For developers working in the Java world, having the ability to play with Grails and Groovy is certainly very appealing. But this alone would not convince me to send my CV over to a new company. We tried to make it very clear about the type of people we wanted and the type of team we are. Continue reading

A Grails developer tries Spring Roo ( pt 1 )

Springsource/VMWare promotes two different application frameworks, Spring Roo and Grails.

As a Grails developer, Spring Roo seems to be more heavily promoted and easily integrated into other deployment platforms than Grails.

For example,

Anecdotally, Roo also has a much nicer shell than Grails.

So how does Roo really compare to Grails? Given the lowered barrier of deployment for Roo, would it make sense to use Roo for new projects instead of Grails?

In this series of posts, I’m going to try going through the Spring Roo 1.1. Cookbook by Packtpub and try port the recipes in the book to Grails.

This would allow me to see any advantages offered by Roo over Grails. Continue reading