[Opensource] CVS Expresso Framework Build fails

[Michael Rimov]

At 12:28 AM 8/20/2002 +0100, you wrote:
>FYI
>
>I am trying to build expresso from CVS and I found out that
>I needed to upgrade Jakarta Ant from 1.4 to 1.5 to use new
>XML rules
>
>I am getting this error

Hi Peter,

Ok, a couple of things taking place... I'm sorry but since the last release 
I've been busy with several projects and haven't gotten to updating the ANT 
documentation.  So here goes a rough draft and I'll eventually will 
incorporate it into a real doc:

First off, the build.xml you want is at the very top level of the 
module.  The other one will be removed shortly (if I haven't already done 
it...)

The default setup expects the following directory structure:

<Your root>
         |--- Expresso Module
         |--- <any component modules such as eForum you might want to build>
         |--- lib Module
                 |-- WEB-INF
                         |-- lib

This can be overridden by your build.properties file in your home 
directory.  If you take a look at the build.xml you'll see all the 
properties that are set at the beginning of the file, so you can go ahead 
and override to your heart's content given the caveat that to this date, I 
haven't tried anything but the default directory structure.

Getting the Classpath set up correctly:

You need the CATALINA_HOME environment variable set up prior to executing 
the build script.  You SHOULD be able to override with build.properties, 
but again, I haven't tested it.  The ant build script will include in your 
classpath anything found in CATALINA_HOME/common/lib for starters.

Then the ANT classpath will have everything (well every jar file, that is) 
added to it that is in the lib module's  WEB-INF/lib directory.

Now the lib module can be either checked out straight from CVS, or you can 
CVS download it.  I plan on writing a quick CVS wrapper in the build to 
retrieve the lib files, in fact, I'll probably do that before I crash tonight.

The targets of biggest interest to somebody getting started with the file are:

build-all - compile all code, build ALL expresso distributions.
build - Clean the output directory and compile everything.
compile - Compile any classes without a clean.
and
javadoc - Build the javadocs for expresso.


RE: esearch... yes, when I first moved the modules, I found out that the 
esearch didn't get put in the right place due to a module directory alias 
in CVS.  I've removed the messed up directories but I haven't been able to 
get to restoring it from the latest code I received from Giovanni.


Hope this helps, and sorry for the holdup
                                                 -MIke