Description Erich Gamma 2001-10-10 21:40:15 EDT

EG (26.09.2001 15:43:02)
PDE puts the startup.jar on the class path automagically. The problem I see
is that the startup.jar comes from the runtime/development workspace. 
For example, I'm running 136 and have code from build 200 loaded in my 
workspace (I don't have 200 installed). When I run my workspace with PDE I'm running it
with the startup.jar from 136 and this could result in surprises.

NOTES:
from DG 
It's a tough question. The class that has 'main' I need to run is UIMain
and it is in startup.jar. Therefore, it belongs to the 'non-plugin' code
that is somewhat hard to handle.

I agree that 1.0 has an issue with the respect to startup.jar, but this
issue will probably not show itself as a critical problem any time soon. It
may become a problem for people that work on 2.0 version of Eclipse while
using 1.0 as a development tool (as you have observed).

I would definitely recommend to open a PR against PDE re this problem. A
possible solution would be for PDE to first try to locate UIMain in the
workspace. If found, it should run it, if not it should run the version
from the development tool space. You are free to comment on possible
problems of this solution.

EG (26.09.2001 15:45:35)
	I agree that the problem will not show up soon. Looking for UIMain
	in the workspace or asking the user once for the startup.jar would make
	the current behavior less magic.