Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 81144 invoked from network); 27 Dec 2002 13:17:36 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 27 Dec 2002 13:17:36 -0000 Received: (qmail 26303 invoked by uid 97); 27 Dec 2002 13:18:48 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 26283 invoked by uid 97); 27 Dec 2002 13:18:47 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 26271 invoked by uid 98); 27 Dec 2002 13:18:47 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Reply-To: From: "Berin Loritsch" To: "'Avalon Developers List'" , Subject: RE: Our site is too big Date: Fri, 27 Dec 2002 08:18:05 -0500 Message-ID: <000801c2adaa$648e5410$f700a8c0@acsdom1.citius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <3E0C5048.4040603@apache.org> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] > > > > Does Forrest have good documentation on getting it to work > and installed? > > Yes. > > http://xml.apache.org/forrest/your-project.html > > Basically untar it, set the FORREST_HOME and add the bin to the path, > and it's done. To use the CVS version, just run "build" first. > > To create a new site, cd into the dir and run "forrest seed". Sounds good. I'll take a look. > > That is my concern. If we offload the tools to a third > party, I don't > > want to have to wrestle with the tool we choose. Maven is > a *build* tool, > > and from what I understand, can delegate to Forrest for doc > generation. > > So as long as it is made **really*easy** for the user to > get up and running, > > I am behind it. > > Both Centipede and Maven can use Forrest for doc generation. > Centipede uses it standard, while Maven need a plugin. > Centipede also doenloads any plugin needed automatically. > > IMHO using Centipede as a build tool coupled with Forrest is > the easiest > for the user, and the most flexible for us, but that's MHO. Gump also > can run centipede projects, while Maven projects are run only > using the > generated ant file. The last time I tried centipede, it was a pain to get working. Maven has an easy declaritive document describing meta-info necessary for building the project. It is very intuitive. Centipede made me feel like I was forced into a box I didn't like for the directory structure. It just wasn't a pleasant experience. OTOH, I haven't looked at Centipede in quite a while. What has changed with it? > DISCLAIMER: I'm the original author of Centipede. I know. ;P -- To unsubscribe, e-mail: For additional commands, e-mail: