[Opensource] Which Build.xml is it ?

[David Herron]

Peter,

You said in another posting that you're working with a freshly checked out
CVS tree.  I did a fresh checkout last weekend, and managed to build both
Expresso and eForum, and get them working, with minor changes to the
build.xml files.

Here's a couple things I do know ...

I used "ant expresso-binary" to build expresso, using the top-level
build.xml file.  Reading through the top-level one you see clearly that it
spawns sub-ant's to do build's in lower level directories.  It's clear
that the strategy is that Expresso and each of the component packages have
a master build.xml in their top-level directory and that is what you use
to do the build of each component.

The USAGE message that's printed from each build.xml is very out of date.
For example it says you can do "ant build", but there is no "build" tag in
the build.xml at all.

In the "expresso-binary" build procedure, there were two failing points.
One is that the cryptography packages cannot be directly distributed by
JCorporate (due to silly US Govt export license stuff), but there is a
"get-crypto" tag that downloads the Bouncycastle package.  The get-crypto
tag isn't mentioned explicitly, but it is in the build.xml.  Getting the
crypto package resolved all the compile problems I had.

The second is that I don't have the Apache FO support, and the
"expresso-binary" procedure runs the "xmldocs" tag which requires the FO
stuff.  I just commented out that section of the build.xml since I don't
care about reading formatted docs.

Getting eForum to build required passing through slightly different
versions of those issues.

I notice that eSearch doesn't have a build.xml, but it does have a full
set of other files.  I remember in your other message you claimed checing
out the "esearch" module came up with an empty directory, but that's not
at all what I saw.  I'm following exactly the directions on JCorporate's
CVS access web page, and have only guest access.

- David




On Tue, 20 Aug 2002, Peter A. J. Pilgrim wrote:

> There are a couple build.xml in the expresso cvs tree
>
> peterp at orchard [103] > pwd
> /new/peterp/expresso
>
> peterp at orchard [104] > find . -name "bui*.xml" -print
> ./expresso-web/build.xml
> ./expresso-web/expresso/doc/build.xml
> ./build.xml
>
> The top level `build.xml' fails to build Expresso on my machine and produces
> over 40 javac compilation errors.
>
> The second level `expresso-web/build.xml' fails because it is missing
> another build file `expresso-web/WEB-INF/src/com/jcorporate/expresso/build.xml'
>
>
> --
> Peter Pilgrim         +-----\ +-++----++----+
> Java Technologist     |     | | ||    ||    | 'n' Shine
>                        |  O  | | ||  --+| ---+
>          /\            | ._  / | | \  \ |    |
>         /  \           | | \ \ | |+--  || ---+ A new day
>        /_  _\  "Up"    | | | | | ||    ||    | is coming
>          ||            +-+ +-+ +-++----++----+
> <home page="http://www.xenonsoft.demon.co.uk/" />
>