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.
When you have the build-impl.xml file open for a project and then right-click and click on "Select in Projects", the project that you last selected in the Projects list is highlighted even if the build-impl.xml belonged to some other project. That behavior is misleading, easily makes the user think that the file belongs to the highlighted project. (I haven't tried if this bug applies to other project files as well.)
well, build-impl.xml is *not* selectable in projects view as it's not part of the node structure in projects view.
I see what you mean. However, build-impl.xml is one of the essential project files, so it associates with the project node quite naturally and that is why the behavior is misleading. If the right thing cannot be activated, then it should not activate anything in the Projects view. build-impl.xml can be located via "Select in Files", but since that is not available in the context menu, I hadn't found it. In most editor programs, I use "Save As..." to find out the origin of an open file but in Netbeans editor that is not available.
(In reply to VesaPa from comment #2) > I see what you mean. However, build-impl.xml is one of the essential project > files, so it associates with the project node quite naturally and that is > why the behavior is misleading. If the right thing cannot be activated, then > it should not activate anything in the Projects view. well, it's a file that is intentionally not part of projects view, because it's more or less internal to netbeans (not to be edited by user, often regenerated by the IDE) > > build-impl.xml can be located via "Select in Files", but since that is not > available in the context menu, I hadn't found it. In most editor programs, I > use "Save As..." to find out the origin of an open file but in Netbeans > editor that is not available. Yes, Files view shows the projects directory structure and it's action (Select in Files) available from main menu or as a shortcut. As Files view is less prominent than Projects view so is it's Select action. as far as I can tell, works as intended.
The behavior is actually more general: If you have any file that cannot be found in the Projects view, Select in Projects operation activates the Projects view and highlights the node that was last highlighted. If you have just opened the project group so that nothing at all has been highlighed in Projects view, then nothing is highlighted. And so this could happen misleadingly with any project file or other file that people could associate with the node that gets highlighted by Select in Projects. Among easy and obvious alternatives, I think the optimal behavior would be to reset the "last highlighted" information when Select in Projects fails so that Select in Projects highlights nothing.
fine, sounds ok to reset highlight and/or write something into status bar that nothing was found. just a minor ui glitch however -> P4
OK, fair enough.
Now is nothing is highlighted when no node found, status bar message was already done. https://hg.netbeans.org/core-main/rev/b6adb808cb44
Integrated into 'main-silver', will be available in build *201402140001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/b6adb808cb44 User: Martin Kozeny <mkozeny@netbeans.org> Log: #234845:"Select in Projects" fails for build-impl.xml -> nothing is highlighted in this case, status bar message was already done.