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.
Summary: | Compile on Save affects JUnit test actions | ||
---|---|---|---|
Product: | java | Reporter: | pribyl <pribyl> |
Component: | Project | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | mmirilovic |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
pribyl
2009-03-26 16:29:16 UTC
what project type? It's on purpose in maven projects for example, there's no native maven way of running just a method. Well, it can be seen on simple J2SE project (sorry I did not specify that in the first post) If you create sample J2SE project with default setting, create a test for Main class and run it. In the result window right-click on the 'testMain (failed)' node. You should see options: Go to Source, Run Again and Debug. Now select Project's properties and turn off Compile on Save. Right click on the testMain node again. Only Go to Source is available now. For the Run/Debug Single Method actions JUnit asks ActionProvider implementation from the project lookup. For the J2SE project it's J2SEActionProvider. So reassigning to java. *** Issue 164079 has been marked as a duplicate of this issue. *** Works fine in dev (NB 7.2), already fixed. It works not completely as expected for me, see http://netbeans.org/bugzilla/show_bug.cgi?id=213887 . |