Paperback: 456 pages
Publisher: Sams Publishing (May 29, 2003)
Product Dimensions: 7.3 x 1 x 9 inches
Shipping Weight: 1.6 pounds (View shipping rates and policies)
Average Customer Review: 3.8 out of 5 stars See all reviews (6 customer reviews)
Best Sellers Rank: #4,085,144 in Books (See Top 100 in Books) #40 in Books > Computers & Technology > Programming > Web Programming > Java Server Pages #1052 in Books > Textbooks > Computer Science > Object-Oriented Software Design #3279 in Books > Computers & Technology > Programming > Languages & Tools > Java
Before I proceed further with the review, I should note that I am the co-author of Java Development with Ant, the book which has been the best selling book about Ant to date. Thus if I were critical of this book, you'd know where I was coming from.But I am not going to be critical -I am going to say nice things about it, and give it 5 stars as anything else would be unfair. This is a really good introduction to Extreme Programming in Java using Ant, Junit and XDoclet.After a quick intro to the concepts of XP, this book follows the story of a team that is using the XP methodology to get stuff out the door. First Ant is introduced, the JUnit -the latter being the key to test-centric development. Then as the chapters progress, the new problems are introduced and the code and the build process refactored and expanded to adapt. I particularly like the chapter where a business merger forces a team reorganisation -organisation change does effect projects, but most software engineering books ignore such events, along with team member dynamics in general. It also repeatedly reinforces the need for automated builds and tests, and has some basic coverage of CruiseControl. CC is the system that keeps our team in check: whenever you break the build, you get email. I get a lot of email.It doesn't go into significant depth in Ant -you will (of course) need the on line documentation, and I would also point my own book. Mostly this isn't an issue -the only place where I had significant differences of opinion was when the book recommended using the task to precompile JSP pages for tomcat. If the authors had tracked the Ant dev mail list, or the open bugreps related to this task, they'd know not to encourage that, because the underlying jasperc doesnt really let you.