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.

Bug 188673 - Neither Test File nor Debug Test File compile test sources
Summary: Neither Test File nor Debug Test File compile test sources
Status: RESOLVED DUPLICATE of bug 189103
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-14 22:33 UTC by jdlee
Modified: 2010-08-02 19:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jdlee 2010-07-14 22:33:23 UTC 
It is my understanding that if if I issue a Test File (Cmd-F6) or Debug Test File (Shift-Cmd-F6) that NetBeans will compile, if necessary, the class then attempt to run/debug the test, but I've found this spotty.  With my project open, if I issue 'mvn clean install' from the command line, then try to test a file, I get something like this:

java.lang.ClassNotFoundException: org.glassfish.admin.rest.JvmOptionsTest
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:169)

If I then issue 'mvn test' from the command line, then retry my debug, it works.  Furthermore, after I issue that, changes to the test are then compiled and picked up for debugging.
Comment 1 Jesse Glick 2010-08-02 19:20:10 UTC 

*** This bug has been marked as a duplicate of bug 189103 ***