On Sat, 10 May 2003, Victor Mote wrote: > Robert P. J. Day wrote: > > > > If you are using a home-grown script that is fine. However, I > > suspect that > > > you are actually using fop.bat or fop.sh at some point. If so, then a > > > cursory examination of those scripts will show that FOP doesn't use your > > > classpath at all, but builds its own. > > > > technically, only half true since FOP initially assigns its LOCALCLASSPATH > > *from* your CLASSPATH, so certainly, if you have an archive on your > > standard CLASSPATH, it will show up in the call through fop.sh. > > Ouch. You are correct. My humble apologies. Thanks for setting me straight, > and this triggers the following off-topic thought: > > <off-topic> Does anyone else think that we should move the following lines > > if [ -n "$CLASSPATH" ] ; then > LOCALCLASSPATH=$CLASSPATH > fi > > to a point below the remainder of the LOCALCLASSPATH building, changing the > middle line to: > LOCALCLASSPATH=$LOCALCLASSPATH:$CLASSPATH > > This would make sure that the FOP-supported libraries appear in the > CLASSPATH before any user CLASSPATH entries.
it would make no difference since, if you take a close look at the loop in fop.sh, the fop/lib jar files are being *prepended* anyway. the end result would be the same. rday --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
