Add required jars to lib directory...?

["Timm, Sean" <ST...@mailgo.com>]

Cocoon has moved to a model where the required jar files for building it are
all located within the lib directory.  I'd like to propose that we either
adopt that model for building FOP, or at least point the classpath to the
resultant directory for the output of both the Xerces and Xalan jar files
(based on relative paths).  Xalan does this for Xerces last time I
checked...

It makes things a lot nicer to build a single project if all of the files
required to build it are contained within it already.

- Sean T.

Re: Add required jars to lib directory...?

[Giacomo Pati <Gi...@pwr.ch>]

"Timm, Sean" wrote:
> 
> Cocoon has moved to a model where the required jar files for building it are
> all located within the lib directory.  I'd like to propose that we either
> adopt that model for building FOP, or at least point the classpath to the
> resultant directory for the output of both the Xerces and Xalan jar files
> (based on relative paths).  Xalan does this for Xerces last time I
> checked...

If xalan has used to do so, it does not do it any more. There where no
build.sh nor build.bat in the CVS. In the build.xml file they describe
what to setup in the CLASSPATH. So xerces.jar + xalan.jar + bsf.jar +
bsfengine.jar make a nice 1 Mbyte of space. I suggest making
distributions from time to time with all of the jars in it for "normal"
users and leave the CVS as it is. It is very easy to make an Ant build
file to pack all together.

Giacomo

> 
> It makes things a lot nicer to build a single project if all of the files
> required to build it are contained within it already.
> 
> - Sean T.

-- 
PWR Organisation & Entwicklung            Tel:   +41 (0)1 856 2202
Giacomo Pati                              Fax:   +41 (0)1 856 2201
Hintereichenstrasse 7                     Mailto:Giacomo.Pati@pwr.ch
CH-8166 Niederweningen                    Web:   http://www.pwr.ch

Re: Add required jars to lib directory...?

[Fotis Jannidis <Fo...@lrz.uni-muenchen.de>]

> Cocoon has moved to a model where the required jar files for building it are
> all located within the lib directory.  I'd like to propose that we either
> adopt that model for building FOP, or at least point the classpath to the
> resultant directory for the output of both the Xerces and Xalan jar files
> (based on relative paths).  Xalan does this for Xerces last time I
> checked...
> 
> It makes things a lot nicer to build a single project if all of the files
> required to build it are contained within it already.

Agreed. On the other: to package xalan and xerces with Fop bloats the size of the Fop 
distribution considerably. And probably many Fop users have Xalan and Xerces in their 
classpath anyway. I rather would offer as a distribution file an additional  self contained 
version of Fop, which contains all jar files needed, and next to this the usual smaller 
version for the average xml.apache.org user. 
Fotis