This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
In the Graph view of pom.xml file, one can double-click on an individual node. This node then becomes the center of the view. However, other nodes lose their connections, and these orphan nodes become red. This is not an issue immediately. But when one wants to restore the view to show the entire graph with all nodes connected, then this seems impossible to do. I double-click on the root node which brings it to the center, but the orphaned nodes are not re-connected - they are still red.
what happens when you click on the background between the nodes?
Clicking between the nodes should work. I tried it on a different computer. Have to get back to the other computer. There it did not work. Meanwhile I close this incomplete until I have more cases.
I can confirm that I can click between the nodes and the graph is not restored. It has happened to me before, and now as you advise me that clicking between the nodes is the definite way to restore the graph, I know there is an intermittent bug. I am working with the maven graph a lot, in fact I think it is a wonderful tool which I would like to demonstrate some time. I checked the log file - there is no bad entry. I just changed the version of some dependency, saved the POM, switched back to the graph, clicked around a bit and suddenly it broke. There is no way to get the orphan nodes back into the tree after the graph is broken.
Created attachment 159976 [details] pom.xml that breaks
could reproduce: - open a pom dependency graph - return to the pom editor, change a dependency version and save - return back to the graph - select a node -> only the node relevant subset of edges will be shown - click somewhere on the background -> all edges should become visible, but aren't the highlight visitor is created once for whole existence of the TC a preset with a DependecyScene, on changing the pom a new scene is created, but the highlight visitor still keeps and works based on the original one
fixed in #1dad921df7fc
(In reply to Tomas Stupka from comment #6) > fixed in #1dad921df7fc nope, actually fixed in #03ae5237ed9d