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.

Bug 42659

Summary: Add filesystems action on project node and source roots
Product: projects Reporter: Martin Entlicher <mentlicher>
Component: Generic Projects UIAssignee: Milan Kubec <mkubec>
Status: RESOLVED INVALID    
Severity: blocker CC: johnjullion
Priority: P2 Keywords: UI
Version: 4.x   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Exception Reporter:
Bug Depends on:    
Bug Blocks: 41448    

Description Martin Entlicher 2004-04-30 17:53:27 UTC 
In the Projects view, there are no filesystem
actions on the popup menu of the root project node
and on Source Packages, Test, etc. nodes. On all
files below there are filesystem actions. This is
inconsistent.

Please add FS actions there like in Files view.
The Project node should perhaps check for any
external source roots, because if there are
external source roots, FS actions would not work
as expected.

This is necessary for VCS actions at least till
VCS project-aware actions are implemented in some
future release.
Comment 1 Jesse Glick 2004-04-30 18:13:22 UTC 
FS actions for package root nodes should be handled by j2seproject etc.

FS action for project root node could also be handled by j2seproject,
or could be done generically in ProjectsRootNode.BadgingNode (which is
getting overloaded by now and should be renamed, BTW).

The former gives more flexibility to project types; the latter
enforces more consistency and is easier for project types to
implement. Ideally we would actually have a helper method somewhere
which would take a "raw" logical view root node and produced a
recommend variant of it with badging, a search provider, filesystem
actions, standardized context menu, etc. This would make it easy for
project types to do things the normal way but still possible to
override this UI if necessary.
Comment 2 John Jullion-ceccarelli 2004-05-03 09:54:37 UTC 
IMHO this should be consistent for all projects or not be there at
all. I don't think the user will understand why VCS actions are
available on the project node in one project but not in another. Also,
I have a hunch that lots of users will be using external source roots,
so that's the one we should maximize for.
Comment 3 Jesse Glick 2004-07-29 21:11:16 UTC 
Not planned for D.
Comment 4 Jesse Glick 2004-09-28 15:36:05 UTC 
No definite plans for E.

See also issue #43233 for VCS actions on package nodes. This is only
about the project node and source root nodes.
Comment 5 Jesse Glick 2008-06-27 00:48:52 UTC 
I think this is obsolete.