Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 55315 invoked from network); 12 May 2002 21:05:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 May 2002 21:05:03 -0000 Received: (qmail 18805 invoked by uid 97); 12 May 2002 21:05:08 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 18789 invoked by uid 97); 12 May 2002 21:05:08 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 18777 invoked by uid 98); 12 May 2002 21:05:07 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3CDED96B.2040200@yahoo.com> Date: Sun, 12 May 2002 22:06:51 +0100 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020510 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon-Phoenix Developers List Subject: Re: documentation updated; help needed References: <1021234591.3779.9.camel@hennep> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Leo, Great work dude. >- The features document (features.xml) (which is brand-new and > incomplete) > I have had a look at this and find it difficult to find a point at which to add things. That is a compliment :-) Also, I have a small problem with the use of the word 'component' and how you use it with 'block'. I see things as services, with the block as the impl. Thus phrases like 'A service could have many block implementions'. >Complaints about the difficulty of doing so will not be listened to as >the process merely consists of getting jakarta-avalon-phoenix from CVS, >editing the xml files in src/xdocs, testing them by typing > >ant docs -buildfile docs.xml > Here here! >in the root of that module, looking at the generated docs in build/docs >to check they are ok, then committing the changes to src/xdocs, and >copying changed files in build/docs over to >jakarta-avalon-site/docs/phoenix and committing those changed files. >(smiling :P) > The copy can be done en-masse with :- ant -buildfile docs.xml site-docs After that, you could cherry pick the ones you want to commit. Regards, - Paul H -- To unsubscribe, e-mail: For additional commands, e-mail: