Thanks for the explanation. I was trying to figure out what I did
differently to cause the classpath change :-)

On 11/6/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
On 11/6/06, Manu George <[EMAIL PROTECTED]> wrote:
> Hi Mohammad,
>                 It definitely did help. On adding the classpath entry
> that problem got resolved but it started asking for some other
> classes. Finally I got it to work. by resetting the classpath by
> clicking on Restore Default Entries in the run dialog box. Somehow the
> classpath had got changed. Thanks for the help

I thought about using JUnit 4.1 annotations in our tests, but it
turned out not be possible with m2 yet. Since it didn't any harm I
left them in the pom.xml.

Sorry for the inconvenience.

Jacek

--
Jacek Laskowski
http://www.jaceklaskowski.pl

Reply via email to