So I just created a simple Maven project with a simple JUnit test case in Eclipse and it seems that it runs the JUnit test case just fine. The project that it is failing on is a very large multi-module project which contains proprietary code. Is there a way I can look into this further to get you the information you need so that I we can find the culprit and/or resolve the issue?
Thanks for you help so far! -Kyle On Fri, Feb 3, 2012 at 1:43 PM, Igor Fedorenko <[email protected]> wrote: > It's hard to tell anything specific without looking at the code. For > some reason JDT java builder does not create .class files at expected > location, it seems. It is possible m2e did not configure the java > project properly and either source or output folders are not what they > should be. It is also possible that java builder fails for some reason. > Or it could be something completely different. > > If you want, please provide a complete standalone example project that > demonstrates the problem and we'll have a look. > > -- > Regards, > Igor > > > On 12-02-03 12:51 PM, Kyle Bober wrote: > >> I just downloaded a fresh instance of Eclipse Indigo SR1 and imported my >> Maven project and attempted to run the JUnit test via 'Run As -> JUnit' >> and got the same outcome. >> >> Class not found >> com.thesearchagency.smb.**service.site.component.**contextprocessing.** >> CustomizationImporterCPTest >> java.lang.**ClassNotFoundException: >> com.thesearchagency.smb.**service.site.component.**contextprocessing.** >> CustomizationImporterCPTest >> at java.net.URLClassLoader$1.run(**URLClassLoader.java:217) >> at java.security.**AccessController.doPrivileged(**Native Method) >> at java.net.URLClassLoader.**findClass(URLClassLoader.java:**205) >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**321) >> at sun.misc.Launcher$**AppClassLoader.loadClass(**Launcher.java:294) >> at java.lang.ClassLoader.**loadClass(ClassLoader.java:**266) >> at >> org.eclipse.jdt.internal.**junit.runner.RemoteTestRunner.** >> loadClass(RemoteTestRunner.**java:693) >> at >> org.eclipse.jdt.internal.**junit.runner.RemoteTestRunner.** >> loadClasses(RemoteTestRunner.**java:429) >> at >> org.eclipse.jdt.internal.**junit.runner.RemoteTestRunner.** >> runTests(RemoteTestRunner.**java:452) >> at >> org.eclipse.jdt.internal.**junit.runner.RemoteTestRunner.** >> runTests(RemoteTestRunner.**java:683) >> at >> org.eclipse.jdt.internal.**junit.runner.RemoteTestRunner.** >> run(RemoteTestRunner.java:390) >> at >> org.eclipse.jdt.internal.**junit.runner.RemoteTestRunner.** >> main(RemoteTestRunner.java:**197) >> >> Seems the 'target/test-classes' directory is still empty. >> >> -Kyle >> >> On Fri, Feb 3, 2012 at 9:48 AM, Kyle Bober <[email protected] >> <mailto:[email protected]>> wrote: >> >> I will give that a try shortly and let you know the outcome. >> >> -Kyle >> >> >> On Fri, Feb 3, 2012 at 9:46 AM, Igor Fedorenko <[email protected] >> <mailto:[email protected]>> wrote: >> >> Are you able to reproduce the problem using fresh/clean install of >> "Eclipse IDE for Java Developers" from >> http://eclipse.org/downloads/ ? >> >> -- >> Regards, >> Igor >> >> >> On 12-02-03 9:30 AM, Kyle Bober wrote: >> >> I am using STS 2.8.1 with 1.0.100 of m2e and I am unable to >> execute me >> JUnit Test cases by simply right clicking on the Java Test >> file and >> selecting -> 'Run As -> JUnit' >> >> I run into the following ClassNotFoundException : >> >> Class not found >> com.thesearchagency.smb.__**service.site.component.__** >> contextprocessing.__**CustomizationImporterCPTest >> java.lang.__**ClassNotFoundException: >> com.thesearchagency.smb.__**service.site.component.__** >> contextprocessing.__**CustomizationImporterCPTest >> 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:__** >> 306) >> at >> sun.misc.Launcher$__**AppClassLoader.loadClass(__** >> Launcher.java:301) >> at java.lang.ClassLoader.__**loadClass(ClassLoader.java:__** >> 247) >> at >> org.eclipse.jdt.internal.__**junit.runner.RemoteTestRunner.** >> __loadClass(RemoteTestRunner._**_java:693) >> at >> org.eclipse.jdt.internal.__**junit.runner.RemoteTestRunner.** >> __loadClasses(**RemoteTestRunner.__java:429) >> at >> org.eclipse.jdt.internal.__**junit.runner.RemoteTestRunner.** >> __runTests(RemoteTestRunner.__**java:452) >> at >> org.eclipse.jdt.internal.__**junit.runner.RemoteTestRunner.** >> __runTests(RemoteTestRunner.__**java:683) >> at >> org.eclipse.jdt.internal.__**junit.runner.RemoteTestRunner.** >> __run(RemoteTestRunner.java:**390) >> at >> org.eclipse.jdt.internal.__**junit.runner.RemoteTestRunner.** >> __main(RemoteTestRunner.java:_**_197) >> >> >> >> If I delete the target directory with the compiled classes >> and make some >> changes to the code in the test class it seems that it is >> not being >> automatically compiled. I have the 'Project -> Build >> Automatically' >> turned on so it is odd that when i make changes to the test >> case code >> that is it not automatically rebuilt. >> >> If I execute the 'Run As -> Maven Test' it does compile the >> test classes >> and places them in the 'target/test-classes' directory. Then >> if I select >> the JUnit Test class java file and 'Run As -> JUnit' it >> executes the >> compiled test class form the previous 'Run As -> Maven >> Test'. If I then >> make additional changes to the JUnit code then 'Run As -> >> JUnit' it does >> not recompile the test class automatically and the changes >> made to the >> class are not reflected in the JUnit execution, Is this a >> bug??? If >> anyone can help me in resolving this it would be wonderful. >> >> -Kyle S, Bober >> >> -- >> Any fool can write code that a computer can understand. Good >> programmers write code that humans can understand. ~Martin >> Fowler >> >> >> >> ______________________________**___________________ >> m2e-users mailing list >> [email protected] <mailto:[email protected]> >> >> https://dev.eclipse.org/__**mailman/listinfo/m2e-users<https://dev.eclipse.org/__mailman/listinfo/m2e-users> >> >> <https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> >> > >> >> ______________________________**___________________ >> m2e-users mailing list >> [email protected] <mailto:[email protected]> >> >> https://dev.eclipse.org/__**mailman/listinfo/m2e-users<https://dev.eclipse.org/__mailman/listinfo/m2e-users> >> >> >> <https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> >> > >> >> >> >> >> -- >> Any fool can write code that a computer can understand. Good >> programmers write code that humans can understand. ~Martin Fowler >> >> >> >> >> -- >> Any fool can write code that a computer can understand. Good >> programmers write code that humans can understand. ~Martin Fowler >> >> >> >> ______________________________**_________________ >> m2e-users mailing list >> [email protected] >> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> >> > ______________________________**_________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> > -- Any fool can write code that a computer can understand. Good programmers write code that humans can understand. ~Martin Fowler
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
