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 49873

Summary: Want API for registering actions on package nodes
Product: java Reporter: Martin Matula <mmatula>
Component: ProjectAssignee: Milan Kubec <mkubec>
Status: RESOLVED WONTFIX    
Severity: blocker CC: jglick
Priority: P3 Keywords: API
Version: 4.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Bug Depends on: 52271    
Bug Blocks: 41535, 49820    

Description Martin Matula 2004-10-04 09:55:17 UTC
Refactoring modules needs to register actions on
nodes in projects view (e.g. Refactor action on
package nodes). These actions should not be
available on nodes in other views (Files view).
Currently we make this work using an ugly hack
(inspecting the active component). However there
is a bug filed against refactoring module (issue
49820) suggesting that we should somehow plug this
actions into the projects view only. For that we
need an API.
Comment 1 Jesse Glick 2004-10-04 16:42:44 UTC
Perhaps a job for Looks. There is nothing special about package nodes
as opposed to e.g. Java source nodes that would deserve a special API.
Comment 2 Jesse Glick 2004-12-15 20:23:52 UTC
Issue #52271 might be appropriate, TBD.
Comment 3 Jan Becicka 2005-01-24 16:04:40 UTC
This issue blocks issue 49820, which is a DEFECT. Accordingly this
issue should be DEFECT as well. Or should be both issues ENHANCEMENTS?
Comment 4 Petr Hrebejk 2005-01-24 16:14:25 UTC
Who decided about a rule that defects can not be blocked by
enhancements? Is there any such rule?
Comment 5 Jan Becicka 2005-01-25 08:02:27 UTC
No there is not such rule. But it sounds logically to me. If some bug
cannot be fixed due to lack of an API, it means (IMO) that lack of API
itself is a bug.
Comment 6 Tomas Zezula 2007-01-10 08:36:36 UTC
Milan is now an owner of the PackageView
Comment 7 Milan Kubec 2007-08-24 16:18:25 UTC
Issue #49820 was closed as INVALID, closing this issue as well. It there is still the requirement please reopen and
describe new usecase. Thanks