Fred,
I’m not sure I follow you. How are
they unusable? When they are executed by the build process, they are first
installed from their assembled state. Specifically, they are installed into a
base Eclipse using the update manager (along with SDK and examples), and then
executed. In fact, using the testing framework to invoke them requires the
test.xml file to be accessible (not jarred), which is why I opted to unpack
test plug-ins on installation.
I suppose we could package them as jars
and simply unpack the test.xml file… But, I’m not sure why it’s
necessary for them to be jarred to be considered usable.
Thanks,
Rich
From:
gmf-dev-bounces@xxxxxxxxxxx [mailto:gmf-dev-bounces@xxxxxxxxxxx] On Behalf Of Frederic Plante
Sent: Tuesday, November 22, 2005
9:28 PM
To: gmf-dev@xxxxxxxxxxx
Subject: [gmf-dev] Problem: M3
Test plug-ins are not jarred
Rich,
The
plug-ins from the M3 test assemblies are not jarred, making them unusable.
Thanks
- Fred
_________________________________
Frédéric Plante
Rational Software, IBM Software Group
770 Palladium Drive, Ottawa,
ON, Canada
tel: (613) 591-7034
