The new minor release of Classycle fixes a bug concerning cases where external and internal classes are from the same package.
The new major release of Classycle (version 1.3) detects dependencies between Java classes caused by Java Generics which couldn't been detected by previous versions.
Classycle (a tool for analysing dependencies between Java classes) searches the constant pool of a class file for finding out on which other classes the analysed class depend on. The new version of Classycle analyses also Java Generics signature information placed by the compiler.
Most of the new features of Classycle 1.2 belongs to the DependencyChecker:
1. Using and defining properties in the dependency definition files.
2. Checking whether sets are empty or not (useful for revealing spelling errors in set definitions).
3. Checking absence of large class/package cycles.
In addition it is now possible to merge inner classes with their outer class. Thus, purely inner class cycles are no longer listed in the report.
The new release of Classycle - an analysing Tools for Java class and package dependencies - generates an improved XML/HTML report:
1) Cycles are sorted in accordance to their size.
2) Classes/packages are linked to the cycle they belong to.
The new major release of Classycle has a new tool: DependencyChecker.
It detects unwanted dependencies between sets of classes. Depedency checking commands are defined in text files using a simple syntax. They are powerful commands for checking whether a layer architecture is broken or not.
DependencyChecker runs from command line or as an Ant task.
The new release is able to deal with class references caused by reflection.... read more
Classycle 1.0 now with Ant task to generate analysis reports! Classes (like JUnit test classes) can be excluded from the analysis.
The new Classycle now analyses also package dependencies and cycles. It goes beyond JDepend and it has a better package cycle detector.
New major release with a new features which helps to improve OO design.