RE: [stellation-res] JRE as project library

["Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx>]

On Mon, 2002-12-30 at 15:47, Jonathan Gossage wrote:
> > >-----Original Message-----
> > >From: stellation-res-admin@xxxxxxxxxxxxxxx
> > >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Mark C.
> > >Chu-Carroll
> > >Sent: December 30, 2002 4:49 AM
> > >To: Stellation-res
> > >Subject: Re: [stellation-res] JRE as project library
> > >
> > >
> > >On Mon, 2002-12-30 at 12:59, Jonathan Gossage wrote:
> > >> For some reason, the file /opt/IBMJava2-14/jre/lib/server.jar
> > >has been added
> > >> as a prerequisite to the org.eclipse.stellation.core project. Is it the
> > >> intent to restrict Stellation to only run with this JRE and if so is it
> > >> available in Windows? In addition the path is hard coded to
> > >something that
> > >> is seldom present on Windows based systems. If libraries such
> > >as this are
> > >> added, would it be possible to use path variables to allow for
> > >different
> > >> user configurations.
> > >
> > >Sorry; that's an error on my part.
> > >
> > >I recently re-installed Linux on my system, and the new version came
> > >with JDK 1.4. In 1.4, the standard lib discovered by Eclipse doesn't
> > >include the java.sql stuff; that's in another jar which isn't added
> > >to the path by default. I tried to set it up using a value derived from
> > >the JRE_LIB classpath variable in the project configuration. If I had
> > >gotten it right, it would have made things work nicely under JDKs that
> > >needed the separate entry to pull in the sql classes, and it wouldn't
> > >have caused any problem for JDKs that didn't.
> > >
> > >Unfortunately, I got it wrong. I'll try to figure out how to get
> > >that right today.
> > >
> > >	-Mark
> > >
> As far as I know, Eclipse 2.1 M3/M4 support finding these jars
> automatically. Check preferences->Java->Installed JRE's and then edit the
> entry for your default JRE. You should see acomplete list of the jars that
> have been detected. I believe that you can also add to the list. This keeps
> everything to do with the JRE independent of the project.

That wasn't it. After going back to look... The usual entry in the
project property for the JRE_LIBs was, for some reason that I fail to
understand, set to "JRE_LIB/core.jar" when I updated to M4. I deleted
all of the entries from the classpath panel of the project properties,
and then re-added the default JRE_LIB entry for all libraries packaged
with the JRE, and all seems to be working. I've checked in it; please
synch with it and doublecheck that it works now. (This Linux
installation that I'm using is so screwed up that I trust nothing
about it to behave correctly. So the fact that it's working here gives
me no confidence. First thing when I'm back in the office after
Newyears is switching back to a sane system.)

	-Mark



-- 
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center  
*** The Stellation project: Advanced SCM for Collaboration
***		http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx  ------- Personal Email: markcc@xxxxxxxxxxx