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.
Due to broken build by tasklist [1] it has been revealed that the module is using reflection to access java module[2]. This needs at least to be documented, better replaced with a standard api. Please use review steps [3] next time you introduce or change (hidden) dependencies between modules. [1] http://www.netbeans.org/servlets/ReadMsg?msgId=877698&listName=broken_builds [2] http://www.netbeans.org/servlets/ReadMsg?msgId=877773&listName=broken_builds [3] http://openide.netbeans.org/tutorial/review-steps.html
It's performance optimalization. There is fallback to standard&lazy EditorCookie.
exec-reflection answer updated.
Can't you have some kind of API between tasklist and java. Do you really have to fallback to reflection?
I added a note to the arch document, so hopefully it was updated with a proper explanation. Note that currently project.xml declares a runtime dep on o.n.m.java. If this is not desired, and the module works without errors or warnings without that dep, feel free to remove it (updating golden files of course). But consider the problems that could be caused by such a use of reflection, e.g. if the java module changes suddenly - what APIs are you missing to be able to get what you need efficiently? Are RFEs for these APIs filed and marked with an appropriate priority?