[Previous entry: "Predictable Delivery: Fear is waste"] [Next entry: "Predictable Delivery: A killer metric"]

02/22/2005: "JUnit Recipes: Great book, less Maven..."

In a recent (positive) review of JUnit Recipes, Carlos Valcarcel wrote:

What I liked the least (well, not so much what I didn't like as what I would have liked to have seen): in a book of this depth it would have been nice to see a web-based application with the various testing layers in place using Ant or Maven scripts to run the tests over the development-life of the example. I keep hoping to run into a tutorial like that, but the sheer scope of the example may be too much to cover without short-changing other areas.

This absolutely would have been a nice thing to add to the book, and if I were a Maven wizard, I would certainly have naturally done things that way. Instead, I am an Eclipse wizard, and so all the examples in the book were prepared using Eclipse, and all the code you can download from Manning's web site is conveniently packaged into Eclipse projects.

I will point out that JUnit in Action talks in some depth about using Maven to build a J2EE project, and so I might even have felt it wasteful to repeat someone else's good work.

To Carlos, I would ask, what is so special about a J2EE project from the perspective of using Maven? What would be in a J2EE/Maven tutorial that wouldn't be in a normal Maven tutorial?