You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tool detects a dependency cycle, but it does not show any details.
Can this be added to show which paths lead to a cycle? Or is this easily spotted in the generated graph?
@wimsymons Thanks a lot for reporting this. Unfortunately such a change cannot be done as the underlying graph visualization library doesn't support it. I am currently on the verge of creating a new branch to start with a revamped functionality that enables users to analyze the graph in Neo4J. The graph visualization will then be completely detached from this tool. Neo4J is an advanced graph visualization library and users can easily perform tiny queries to get that what they need - such as service cycles, package dependency cycles and many more. I will keep you updated on the progress.
The tool detects a dependency cycle, but it does not show any details.
Can this be added to show which paths lead to a cycle? Or is this easily spotted in the generated graph?
I looked at the CycleDetection class, but it has no documentation on how this works and Javadoc of the TarjanStronglyConnectedComponents class from https://data.graphstream-project.org/api/gs-algo/current/org/graphstream/algorithm/TarjanStronglyConnectedComponents.html, did not make me any wiser.
The text was updated successfully, but these errors were encountered: