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.
I noticed that the currently open pom.xml and its direct dependencies are indicated via shading on the dependency graph. And that is useful indeed. So that gave me this idea. Would it be possible to also indicate the currently open projects visually somehow?
It would be also useful, that you can jump to the project when you doubleclick on such a node.
Created attachment 135609 [details] Proposed patch I like to propose a patch to solve this issue. The patch adds project icons for open project to the ArtifactWidget. See screenshot. I had to add a dependency to projectuiapi to get the open projects. I am not sure if I used the most efficient way to get the project icon. Please review, rewrite and commit if appropriate.
Created attachment 135610 [details] Patch in action
ideally the map of artifact/file to open project icon would be calculated just once and not repeatedly for each widget. with 100 projects opened and 200 nodes in graph, the calculation is too costly in AWT (as we already have severe problems with layouting)
Created attachment 135659 [details] Proposed patch v2 @Milos: Please review the updated patch! When creating the scene the icons are gathered once and hold within a map.
(In reply to comment #5) > Created attachment 135659 [details] > Proposed patch v2 > > @Milos: Please review the updated patch! When creating the scene the icons are > gathered once and hold within a map. @Milos: Another thing which made me think of. In the patch v2 the icons are looked up via "projectIcons.get(artifact)". This won't work when there is a pom.xml (A) with packaging 'ejb' and a pom.xml (B) depends on (A) without defining the type tag 'ejb'. Is this a valid scenario?
thanks for the patch. i will apply v2, it seems to work fine. > @Milos: Another thing which made me think of. In the patch v2 the icons are looked up via "projectIcons.get(artifact)". > This won't work when there is a pom.xml (A) with packaging 'ejb' and a pom.xml (B) depends on (A) without defining the type tag 'ejb'. Is this a valid scenario? speaking for myself - not sure if it is. Let's deal with it in case it appears as a problem ...
fixed in core-main #aa789c82dad3
Integrated into 'main-silver', will be available in build *201407190718* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/aa789c82dad3 User: Tomas Stupka <tstupka@netbeans.org> Log: Issue #217106 - Patch for: Maven dependency graph visual indication - show icon for open projects