This post originated from an RSS feed registered with Java Buzz
by Padraic R.
Original Post: depend in ant
Feed Title: plog
Feed URL: http://sedoparking.com/search/registrar.php?domain=®istrar=sedopark
Feed Description: Padraic Renaghan's musings about (mostly) java software development
Been trying to figure out exactly what the <depend> task in ant does. Having trouble generating a test case where the <javac> task built-in dependency checking would miss something that the <depend> task would catch. I frequently get results where the <depend> task (which runs first) reports zero out of date files deleted, the subsequent <javac> task (running jikes) reports 1 file compiled. I would always expect the <depend> task to at least find as much out of date as <javac> and frequently more - that being the whole point of the <depend> task. Am interested in a simple test case where <depend> catches something that <javac> won't.
All this brought about by reading Erik Hatcher's excellent book, Java Development with Ant. All the great reviews of this book are accurate. No need to restate, I'll just say go buy the book and read it if you want to learn better ways and best practices around java development, build, and deployment.
Along those same lines, while I'm thinking about it, the Log4j manual/book is also a great purchase. Learn the finer points. Good for beginners and those who want to learn some of the more powerful features, especially around customization. Help support the Log4j project by purchasing the book.