Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 34368 invoked from network); 2 Oct 2003 04:54:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Oct 2003 04:54:41 -0000 Received: (qmail 54887 invoked by uid 500); 2 Oct 2003 04:54:19 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 54828 invoked by uid 500); 2 Oct 2003 04:54:19 -0000 Mailing-List: contact dev-help@avalon.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 dev@avalon.apache.org Received: (qmail 54815 invoked from network); 2 Oct 2003 04:54:19 -0000 Received: from unknown (HELO smtp.noos.fr) (212.198.2.122) by daedalus.apache.org with SMTP; 2 Oct 2003 04:54:19 -0000 Received: (qmail 9566 invoked by uid 0); 2 Oct 2003 04:54:29 -0000 Received: from unknown (HELO apache.org) ([::ffff:212.198.17.4]) (envelope-sender ) by ::ffff:212.198.2.122 (qmail-ldap-1.03) with SMTP for ; 2 Oct 2003 04:54:29 -0000 Message-ID: <3F7BB012.6030100@apache.org> Date: Thu, 02 Oct 2003 06:56:50 +0200 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Avalon Developers List Subject: Re: BugZilla List References: <03334AAF1DF8D2119B1000A0C9E32F58065EF996@us-pb-xmsg-2.am.sony.com> In-Reply-To: <03334AAF1DF8D2119B1000A0C9E32F58065EF996@us-pb-xmsg-2.am.sony.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Farr, Aaron wrote: > Forrest is definitely better, but with maven, anakia docs are just so > much > more convenient (plus you get the generated reports). > > >My original idea in reorganizing the site was to stay with the main site as >Forrest based (so that articles and documentation could take advantage of >the better format) and move all project-based docs to maven (so as to take >advantage of maven's integrated reports, etc). > >If we can fix this current bug, then I don't think there's any real problem >with this approach, but I'm open for other ideas. > I'm basically in favour of one simple solution across all of avalon. Unless we have a clearly identified need for something special - the overhead of two build solutions just means a higher barrier to maintaining the site. Stephen. -- Stephen J. McConnell mailto:mcconnell@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org