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.
Do you really need ProjectEditorSupport.Env to be public? I doubt so, that is why I suggest to remove it from the API and have it a private impl until somebody needs to update it.
I don't think so, clients have to subclass it and provide implementation of findSupport() abstract method. BTW, why is the Env innerclass public in *EditorSupport classes in openide? Anyway, I'll think about it a bit more, maybe we shouldn't blindly copy openide concepts ;-).
Better than copying is learning from openide mistakes. Why is CloneableEditorSupport.Env public is easy, because it needs to be implemented. Why is DataEditorSupport.Env public is questionable, probably I thought that somebody will want to reuse it for editing other than primary file of a data object. But as ProjectMember has only one file, I do not think that such a need applies to projects. In my opinion the Env can be either completely hidden or created using a factory method.
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped.
Marking issue as VERIFIED --->
---> CLOSED