On Thu, Dec 18, 2014 at 5:29 AM, Bob Tarling <[email protected]> wrote: > > > My end goal is actually to determine package dependencies. I have a large > application that I'm sure has cyclic dependencies between packages and I'd > like to demonstrate that problem to the team I work with before we tackle > how to resolve it and split the app to smaller jars. >
The tool I used to do this analysis for ArgoUML itself (although we never tackled removing the package cycles) was Classycle: http://classycle.sourceforge.net/ It is available as an Eclipse plugin as well as standalone tool. One nice addition since the last time I used it is support for Dependency Definition Files. This allows you to describe allowable dependencies (e.g. your architectural layers) and it will check for violations. http://classycle.sourceforge.net/ddf.html Looking at http://argouml.tigris.org/source/browse/argouml/trunk/tools/classycle/ it looks like it's been 7-8 years since I used it for ArgoUML. IntelliJ's dependency analysis looks pretty powerful too (although I haven't used it): https://www.jetbrains.com/idea/features/dependency_analysis.html While adding dependencies to the Java reverse engineering may be useful for other stuff, it's not how I'd recommend finding package cycles. A tool designed for that purpose will do a better job. Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=3092993 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
