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.
Build: NetBeans IDE 6.7 (Build 200906241340) VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08 OS: Linux, 2.6.28-14-generic, i386 User Comments: mjr_1974: Re running a failed JUnit test Stacktrace: java.util.MissingResourceException: Can't find resource for bundle org.openide.util.NbBundle$PBundle, key ACTION_run.single.method at java.util.ResourceBundle.getObject(ResourceBundle.java:384) at java.util.ResourceBundle.getString(ResourceBundle.java:344) at org.openide.util.NbBundle.getMessage(NbBundle.java:631) at org.netbeans.modules.java.j2seproject.J2SEActionProvider.invokeAction(J2SEActionProvider.java:519) at org.netbeans.modules.groovy.support.LookupMergerSupport$MergedActionProvider.invokeAction(LookupMergerSupport.java:111) at org.netbeans.modules.junit.output.TestMethodNodeAction.actionPerformed(TestMethodNodeAction.java:73)
Created attachment 85497 [details] stacktrace
Can you please provide exact steps to reproduce? Do you you use groovy in your project?
I would say this is another symptom of already fixed MRE in org/netbeans/modules/java/j2seproject/Bundle.properties see: http://hg.netbeans.org/main-golden/log/7f7aefeba362/java.j2seproject/src/org/netbeans/modules/java/j2seproject/Bundle.properties key ACTION_run.single.method is really missing there.
yes, the key is really missing, but I cannot figure out, which action is broken.
Sorry, but I cannot provide you with steps to reproduce. I got this exception once and the only thing I did was to run the tests and try to re-run one that failed. I'm not using Groovy in my project: it's a pure J2SE one.
fixed in: http://hg.netbeans.org/jet-main/rev/73ed3e4a5443
Build: NetBeans IDE 6.7 (Build 200906241340) VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08 OS: Windows XP, 5.1, x86 User Comments: Stacktrace: java.util.MissingResourceException: Can't find resource for bundle org.openide.util.NbBundle$PBundle, key ACTION_run.single.method at java.util.ResourceBundle.getObject(ResourceBundle.java:384) at java.util.ResourceBundle.getString(ResourceBundle.java:344) at org.openide.util.NbBundle.getMessage(NbBundle.java:631) at org.netbeans.modules.java.j2seproject.J2SEActionProvider.invokeAction(J2SEActionProvider.java:519) at org.netbeans.modules.groovy.support.LookupMergerSupport$MergedActionProvider.invokeAction(LookupMergerSupport.java:111) at org.netbeans.modules.junit.output.TestMethodNodeAction.actionPerformed(TestMethodNodeAction.java:73)
Created attachment 86544 [details] stacktrace
Any plan to release as 6.7 patch? I can not re-run a single on 6.7.1, no workaround.
This bug is marked as fixed on 30 July, but it only started happening to me in 6.7 (64bit linux) after the latest automatic updates I got (issued in the last 1-1.5 weeks). Also at the same time the the 'Run again' and 'Debug' actions not longer appear on the context menu for individual test methods unless that test failed, which would be frustrating if the actions weren't currently broken due to this bug.
The fact that this and other problems with the "Test results" panel still hasn't been deployed in an update for 6.7 (or 6.7.1) has almost made me give up on netbeans altogether. The only thing that currently works reliably is whether or not the tests pass. Failure messages don't always have the actual cause displayed and instead have 'Caused an Error' followed by a filename and line number (sometimes incorrect). Sometimes stack traces are cut off. Bottom line is that currently I can't use and updated netbeans for unit testing and have had to resort to installing a clean 6.7 with no updates allowed. I'm just wondering why the target for this fix (and hopefully the others) is 6.8 when the breakages to the 'Test results' panel were merrily rolled out as part of a regular update (many months ago). Especially when the problems are serious enough to make it easier to debug unit tests on the command line than to use netbeans.