[news.eclipse.tools.hyades] Re: Classpath problem in JUnit profiling

[Jiaqi Guo <jiaqi@xxxxxxxxx>]

Yes, I am. Which dll file are you talking about? Let me double check it.

If dll file is missing in path, I guess the error message should not be 
ClassNotFoundError, and all tasks running with probekit should break. 
While I can run java applications and some other test cases and get 
reports without any error.


Thanks
Jiaqi

Manmohan Gupta wrote:
> "run the same test with profiling" means you are instrumenting your test
> case code using probekit? Then maybe probekit dll is not in your path.
>
> "Jiaqi Guo" <jiaqi@xxxxxxxxx> wrote in message
> news:ck1o1g$oc4$1@xxxxxxxxxxxxxx
>
> > I have a junit test case which runs in eclipse 3.0.1. The  test case
> > extends org.codehaus.plexus.PlexusTestCase which is nothing but a base
> > test case in another jar file sitting in classpath.
> >
> > Funny thing is when I run the same test case with profiling, I got a
> > ClassNotFoundError which told me the base class of test case
> > org.codehaus.plexus.PlexusTestCase is not found.
> >
> > All settings are default. the classpath simply is default classpath plus
> > JRE System library.
> >
> > Is there anything I can try to make it work?
> >
> >
> > Thanks
> > Jiaqi