Re: [stellation-res] ... PDE JUnit support

[Jim Wright - IBM Research <jwright@xxxxxxxxxxxxxx>]

At 07:58 PM 11/26/2002, Jim Wright - IBM Research wrote:
Re: JUnit and Eclipse.

> After installing M3, I had to re-install the PDE JUnit plugin
> (since it's not part of the standard Eclipse release).
> I'm having a bit of trouble getting it to run, so I haven't been able to
> test the updated JUnit tests yet.  I'll post a followup when I've resolved 
> that.

I have JUnit PDE working again, using the Eclipse 2.1 M3 build.

Several points are noteworthy:

1. The 2.1 org.eclipse.pde.junit plugin should now be used as-is.
With Eclipse R2.0.x, it was necessary to fix an import and rebuild
the pde.junit plugin.  With 2.1 M3, that will break the PDE JUnit plugin.
(no surprise here)

1a.  On second thought - I had some kind of problem (real or phantom, not sure)
using the pde.junit zip posted on eclipse.org (URL below).  I actually 
checked out
the current source from the main Eclipse CVS tree, built it locally, and 
then copied
the relevant bits into eclipse/plugins/org.eclipse.pde.junit

2. You must first update classpaths for everything (and make sure all required
projects are present as binary projects (or source, your preference) in the 
workspace.
Then, you must rebuild all projects absolutely from scratch.
Otherwise various bits of cached data will not be refreshed.

FYI, I ran into a glitch where Eclipse stubbornly refused to recognize an 
updated version
of the ...pde.junit plugin.xml file.  Somehow, the old plugin metadata had 
been cached
and Eclipse did not consider it to be stale.  I had to exit Eclipse, delete 
the pde.junit
plugin folder (from eclipse/plugins), restart Eclipse, exit Eclipse, and 
only *then*
copy the updated org.eclipse.pde.junit folder and contents into 
eclipse/plugins. (see 1a above).

Once the plugin is building/loading, you will need to update your JUnit
configurations.  When I started testing, Eclipse complained that the
'workspace was not set properly' (or some such).  It was necessary
to browse and specify the location of the test workspace.
Previously, Eclipse just created a folder nested under the 'temp' path.
Now, you can (and must) specify the location of the test workspace.
This is a change for the better, but puzzled me for a bit.

Once all this was done, the Client Core JUnit tests worked as before.
I expect to resume Client Core work later today; maybe over the next 
several days....
with some time out for Thanksgiving (tomorrow) and my wife's birthday 
(Saturday).

Happy Thanksgiving to all (please substitute appropriate localized greeting,
or simply 'Enjoy the last of the fall: winter's coming!")

- Jim

--
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email: 
jim.wright@xxxxxxx