I Will Use Grails mockDomain or Die Trying
As part of my effort to ramp up my Grails productivity I have been trying to get better at using the framework’s new domain mocking feature. Simply stated, what this new Grails 1.1 feature enables you to do is test the persistence and validation behavior of your domain classes without the overhead of spinning up a container. I like to run my tests constantly as I write code as this gives me early feedback when I screw something up. Domain mocking really helps in this regard.
In trying to get mockDomain to work I’ve had to deal with a number of snags, but I’m finally seeing some light at the end of the tunnel. Hopefully this blog entry will help you avoid getting caught on some of the rough edges Read the rest of this entry »
Wish List: Running Grails and Groovy from the Maven Repository.
The Need For A Separately Installed Grails Instance Outside of the Maven Repo
I recently began using the excellent maven-grails plugin, and It works quite well.
The documentation for the plugin suggests that “you should unset the GRAILS_HOME environment variable when running Maven with a Grails project. This is because you no longer need to install Grails separately to use it with Maven!” True enough. But currently when you are not using Maven to run Grails you can’t do without the GRAILS_HOME setting and installations of Groovy and Grails outside of your local Maven repository. Read the rest of this entry »
