The number of dependency cycles has been shown to have a stronger correlation with code churn than God classes. Including classes that are involved in dependency cycles in the analysis would be very helpful.
Identify class cycle groups and prioritize based on average churn of all classes involved in the cycle.
Identify all classes referred to by each class with JavaParser / JavaSymbolSolver (package name + class name) -- see https://stackoverflow.com/questions/22684264/how-get-the-fully-qualified-name-of-the-java-class
Identify strongly connected components (cycles) with JGraphT: https://jgrapht.org/guide/UserOverview#graph-algorithms
The number of dependency cycles has been shown to have a stronger correlation with code churn than God classes. Including classes that are involved in dependency cycles in the analysis would be very helpful.
Identify class cycle groups and prioritize based on average churn of all classes involved in the cycle.
Identify all classes referred to by each class with JavaParser / JavaSymbolSolver (package name + class name) -- see https://stackoverflow.com/questions/22684264/how-get-the-fully-qualified-name-of-the-java-class
Identify strongly connected components (cycles) with JGraphT: https://jgrapht.org/guide/UserOverview#graph-algorithms