forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: packaging our tools
Date Tue, 02 Nov 2004 21:36:37 GMT
On Nov 2, 2004, at 1:19 PM, Dave Brondsema wrote:
<snip>
> If we build a release of forrest, what happens to this .zip file?  I
> imagine it would be something like this:
> * As part of the main forrest build, the XXE build.xml is called
> * The .zip file that is created is moved to _____

This seems dangerous. Why not just "build" it to: 
forrest/tools/xxe/xxe-tool.zip

> * Everything (src, and built files (build/xml-forrest.jar and the .zip 
> in
> question) is packed in to one apache-forrest-0.7-dev.zip
>
> And can we make this .zip file available seperate from forrest?  There 
> is
> a current need for this since 0.6 does not include a built XXE
> configuration.  Future need may continue to exist, because people may 
> want
> to edit document-v13/20 files without installing forrest.  This is the
> case at the company I work for, because the writers commit their 
> changes
> to CVS and then we run forrestbot on our server.

Sounds cool. Does it make sense to place a copy of your forrestbot in 
the forrestbot/ dir as another example?

Web Maestro Clay
-- 
Clay Leeds - <cleeds@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>


Mime
View raw message