Because Classycle isn't a visual tool it is not so easy to see how a cyclic dependency ctually looks like. If only a few classes are involved you can do it by hand. Otherwise a visual tool for graphs is needed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have created successfully the XML report. I am trying to find an easy way to find circular-dependencies.
The report is nice, that it tells me where circular dependencies *might* be present, but leaves some amount of work to acutally find the defect.
Is there something I am missing here?
Because Classycle isn't a visual tool it is not so easy to see how a cyclic dependency ctually looks like. If only a few classes are involved you can do it by hand. Otherwise a visual tool for graphs is needed.