Creating an Eclipse-based Groovy Development Environment for TDD
Within the system I'm building at Broadchoice, we're exploring the use of Groovy, Spring, and Hibernate in combination. The first step in building a system using this stack is creating an Eclipse-based environment in which we can write and test our code. To help people do this, I've published a Google document entitled Creating an Eclipse-based Groovy Development Environment for TDD.
As it doesn't contain any "technical secrets" (we don't really have the concept of a technical secret at Broadchoice!), I thought it'd be handy to share it with the world.
I've still got more to document, including how to integrate TestNG tests with Spring and how build (and effectively test!) a Hibernate-enabled Groovy+Spring project. A lot of this is the result of reading multiple books and a good deal of Googling / piecing together information, so I hope you enjoy it in distilled, ready-to-consume formats!


thanks for the comment subscribe feature, ray!
The one-line answer from my end is: clustered caching, capabilities of other Java frameworks for which there's no CF equivalent, and creating a more easily distributable (no license fee) JEE application.
What didn't you like about Grails?
<a href="http://www.poweredbypulse.com/profile_detail.php?blueprint_id=rcb-17555&realm_id=2">
<img src="http://www.poweredbypulse.com/images/pulse-blue.png" alt="Check out Pulse" border="0">
</a>
Should save everyone some time running down plugins and figuring out configurations. FYI, you can set up your own software stacks with Pulse and share them as well.
Todd
http://www.ibm.com/developerworks/java/library/j-c...