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.
The fix for issue 28536. Is applied too late during the startup sequence. There is at least one scenario where some module code is called in AWT without the context classloader being properly set. Please check my suggested patch to 28536 for moving the code in question up in the method Main.initializeMainWindow(). I don't insist on the patch being exactly like I suggest but only to make sure that before any module code is called in AWT thread the hack described in 28536 should be applied. Assigned directly to Jesse since he fixed the previous issue.
Could you attach a -u format diff please? The contextless diff is hard to verify.
Created attachment 11359 [details] Proposed patch
Please note that I have changed invokeLater to invokeAndWait. Don't know whether that is really needed. As I said with this patch at work my xtest tests now running without problem. Could this be done even earlier? e.g. as soon as the module system knows the classloader? But maybe only in case something goes to AWT not to initialize AWT in a non gui session. So the method initializeMainWindow is probably the right place ...
Will use invokeAndWait; would be necessary only if something in window mgr init uses it too (which I don't know about). Would rather not put this code elsewhere - as you say, do not want to initialize AWT unless it will be used.
Did I mark this fixed? Sorry, not yet.
committed Up-To-Date 1.169 core/src/org/netbeans/core/Main.java
closed