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.
Should be P2 but leaving as P3 temporarily to avoid needing to waive for 4.0. The editor module should not depend on the project API. Cf. similar issue #50815. If the editor module is refactored into smaller pieces it would perhaps be OK to have some GUI-only piece depend on projectapi if the ultimate user goal is really to behave differently depending on whether a CP root is owned by a project or not. But I think this is probably incorrect anyway; this is probably a hack and should be solved properly at a different level. The editor module should not care that projects are used to specify classpath information; other modules should be free to have special ClassPathProvider's that are fully on par with project implementations.
Target milestone is obsolete, please re-evaluate. Thanks.
Currently the editor/bookmarks uses saving of bookmarks into project. In addition java/editor uses FileOwnerQuery.getOwner() to satisfy "Show Non-project classes" in "Goto Class" dialog. After the editor module split the editor's core (editor and editor/lib) does not depend on projects API anymore. Closing as fixed. Please reopen if additional action is needed.
Sounds right. The usage of FOQ from Goto Class seems justified.