Hi All,

I'm slowly starting to chip away at a queue of new features.  Whenever I have a few significant changes, I'll drop a new version.  This time around, I added one new feature and deprecated one old "feature":

- Based on the results of the poll, source-file analysis is now deprecated.  If JDepend runs across a .java file during analysis, you'll see a deprecation warning printed to standard error.  It only happens the first time a source file is noticed during any particular run.  Please start pointing JDepend at directories containing class files to ensure the best results.  In the next version, source-file analysis won't be an option.

- The new feature is a request Bob Martin made a while back.  Sometimes you have packages that are not subject to change, such as java.lang, that you'd like always to fall directly on the main sequence.  Now you can preset a volatility (V) value on a package-by-package basis, either programmatically or using the jdepend.properties file.  More info on this feature is available at <http://www.clarkware.com/software/JDepend.html#customize>.

The latest version containing these changes is available at:
  
    http://www.clarkware.com/software/JDepend.html

In the next version, I hope to take a closer look at cycle detection and make the DependencyConstraint a bit more usable.  And now that class-file analysis is destined to be the only way, supporting jar and zip files is also something I'm planning to get in real soon now.  Also, the folks at Maven submitted an excellent request (along with source code!) to report the source file name corresponding to the class file.  That would allow you to cross-reference the classes (and inner classes) back to their source file.

Enjoy!

Mike

-- Mike Clark
http://clarkware.com
(720) 851-2014