This bug was originally marked as duplicate of bug 216053, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.
Build: NetBeans IDE Dev (Build 201209110001)
VM: Java HotSpot(TM) Client VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b11
OS: Windows 7
javydreamercsw: Right click on code to get menu. Maven index unpacking was going on the background.
Maximum slowness yet reported was 6822 ms, average is 6822
Created attachment 124182 [details]
JUnitMethodRunnerProvider should not call javac parser from AWT EDT.
Created attachment 126407 [details]
saved persistence.xml file
Created attachment 126541 [details]
In none of the slowness reports can I spot any reference to JUnitMethodRunnerProvider. On the last two the probel seems to originate from CompilationController and RenameSupport. re-assigning for evaluation. Thank you
It's in javydreamercsw snapshot:
org.netbeans.modules.junit.actions.JUnitMethodRunnerProvider.canHandle() 57.85053 3,500 ms (57.9%) 3,500 ms
The rest should go back to dusan.
true. sorry I missed that. In that case regarding the javydreamercsw snapshot is a duplicate of bug 213998. re-assigning back to Dusan to handle the rest. Thanks
OK - so the next is JPAProblemFinder that should not call javac parser from AWT EDT.
snapshots should be rearranged in this case, will keep only persistence related here
I'm not sure what may mean 'next is persistence' as see no reolution on other cases, but as initial report isn't related to persistence and there is only 2 out of 8 for persistence, create new issue #221024 for this 2 reports and push issue back without persistence for additional evaluation.
The remaining exception report is already fixed in the current dev build.