On Mon, 15 Oct 2001 04:24, Paul Hammant wrote:
> Peter,
>
> >nope - the problem is the build file writer ;)
>
> Swine ;-)
awww
#8-D
> OK, Catalina's build forces the existance of build.properties and a
> template is provided. It does not offer much by way of textual help,
> but few downloads and assigments the build will work. I am not sure it
> is perfect as the unless="" help does not give much explanation. For
> the case above, xerces.jar is needed for some blocks. It could be in
> one of three places :
>
> 1) ../../jakarta-avalon/tools/lib/xerces.jar (cornersone, logkit,
> excalibur etc via CVS)
> 2) ../../../../jakarta-avalon/tools/lib/xerces.jar (demo, bay, ftpserver
> & jesktop via CVS)
> 3) ${ANT_HOME}/lib/xerces.jar
> 4) ${AVALON_TOOLS}/lib/xerces.jar
>
> It all depends on whther you've CVSed or downloaded and if ou CVSed, did
> you put the project roots in the same dir..
>
> Perhaps we could specify the full path in ant.properties (or
> build.properties like Catalina) and give extensive help if dependancies
> are not satisfied during some pre-compilation step.
An extensive walk through (ie keeping giving messages till all the required
jars are present) works for me. However I still wouldn't mind keeping the
jars that change often, we use CVS versions of or are hard to get in CVS.
--
Cheers,
Pete
*------------------------------------------------------*
| Despite your efforts to be a romantic hero, you will |
| gradually evolve into a postmodern plot device. |
*------------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
