HI AJ, I use "Run as JUnit test" otherwise I do get some classloading issue (unable to register RI, etc.). I don't know why, it must be an issue with Eclipse. Haven't had time to investigate this more. Anyway, the first option works very well for me, allows debugging, etc.
Best regards, Jerome > -----Message d'origine----- > De : A.J. Barnes [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 25 octobre 2006 10:56 > À : [email protected] > Objet : RE: Eclipse again > > Just to check Jerome, are you running as a JUnit Test or a > JUnit Plug-in > Test? > > If run as a plug-in test a lot more goes on, including > starting up a new > test workbench and all the classlaoders associated with that - so you > acutally see a new instance of Eclipse running. This really > does seem to > make a difference. > > All of my plugins have been created via the > New->Project->Plugin project > (specifically as plugins for a RCP project). > > AJ > > Quoting Jerome Louvel <[EMAIL PROTECTED]>: > > > > > Hi AJ, > > > > In the Restlet distribution, there is a > > "/src/com.noelios.restlet.test" > > directory that contains a plug-in project that serves as a suite of > > JUnit > > tests. It is working fine within Eclipse, even when I run the tests > > with > > "Run as JUnit test case...". > > > > I'm not sure what goes wrong in your case. Could you give > me detailed > > steps > > to reproduce, or a sample project. > > > > BTW, in order to have a full Eclipse plug-in project, you need a bit > > more > > that a MANIFEST.MF file. Some special entries are also added to > > .project. > > The best way to convert a Java project into a Plug-in > project is to use > > "PDE > > Tools/Convert Projects to Plug-in Projects..." menu entry. > > > > Best regards, > > Jerome > >
