Hi,

 

Sorry for the delayed response. Am not reproduce this problem anymore
with latest pax exam.

 

Regards

Sathya

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Toni Menzel
Sent: Thursday, September 08, 2011 8:12 PM
To: General OPS4J
Subject: Re: Weird ClassNotFoundException with pax exam 2.1.0

 

Hi,

 

Sathyakumar uses pax runner container (he wrote that).

So what i think is important:

- can you provide the names ? at best of cause a full log output. (at
least stack trace)

- update to 2.2.0 at least (though should not matter, but its just not
good using the outdated version. (best is 2.3.0-SNAPSHOT as we will
release this in some form or the other very soon) 

- can you repeat this behavior ?

- any special @Configuration ? like setting workingDirectory manually?

 

Toni

 

 

On Thu, Sep 8, 2011 at 4:37 PM, Harald Wellmann
<[email protected]> wrote:

No, you can have any number of test methods per test class.

The problem must be somewhere else. Which OSGi framework(s) are you
using for your test? What happens when you comment out the @Test
annotation on your first method so that Exam only sees the second one?

Best regards,
Harald

2011/9/8 Sathyakumar Seshachalam <[email protected]>:

> Hi,
>
>
>
> I am running a unit test (@Junit4TestRunner.class) which has two @Test
> annotated methods both of which take a BundleContext as argument.
Weirdly
> the second test method fails with a "ClassNotFoundException" of the
test
> class itself, while the first one executes without a problem. If I
copy and
> paste contents of the second test method in to the one, it all works
fine.
> Does this mean I can only have one test method ? note am using pax
runner as
> the container.
>
>

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general





 

-- 
Toni Menzel Source <http://tonimenzel.com> 

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to