In your new book, what do you cover under the topic of �Monitoring� Java applications? Are you referring to maintenance of the product after deployment or are you referring to automated tools monitoring the performance of the application?
Also, do you talk about integration of Ant with ClearCase in your book?
The Monitoring chapter covers both monitoring the results of scheduled builds (email, RSS, and visual devices such as lava lamps) and monitoring running programs that have been installed or deployed. I don't cover performance monitoring per se, but it's a specific case of a more general type of monitoring.
My experience with performance monitoring has included sprinkling logging statements throughout a program and injecting bytecodes into classes as they are loaded into the JVM (a dynamic form of sprinkling logging statements). I don't cover the latter because it's beyond the scope of the book. Sprinkling logging statements manually could be achieved using log4j, for example. You could also monitor performance such as a web page's average response time using a debug command issued to a hidden performance web page, or through JMX.
To be consistent throughout the book, I needed to pick a version control system. I use CVS and the version control book in the Starter Kit goes into great detail on how to use CVS, so I picked CVS. So I don't talk about ClearCase in the book, but I would hope that the concepts and practices are easy to transfer to a ClearCase environment.
Mike Clark<br />Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0974514039/ref=jranch-20" target="_blank" rel="nofollow">Pragmatic Project Automation</a>