🚀 go-pugleaf

Craig:

The JDK shouldn't be a library -- that's why we implemented JDK
switching.  That would most definitly cause the problem, though. 
Classpath gets resolved on a first found basis and when you use tools
from one JDK with classes from another it can get messy (esp. if you
are trying to use the older tool with the newer jdk -- Java isn't
always forwards compatible).

-Rich

Craig Patchett wrote:
> 
> Richard Wilkman wrote in message <359BA8F7.7964AD85@inprise.com>...
> 
> >It sounds like one of the libraries referenced in the project has an
> >instance of classes.zip or some other JDK in some other location.
> 
> I don't think that's the case. I was able to resolve the problem though by
> adding the JDK to the top of the library list.
> 
> Craig

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=