Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 54467 invoked by uid 500); 25 Mar 2003 11:05:10 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 54454 invoked from network); 25 Mar 2003 11:05:10 -0000 Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65) by daedalus.apache.org with SMTP; 25 Mar 2003 11:05:10 -0000 Received: (qmail 17299 invoked from network); 25 Mar 2003 11:05:20 -0000 Received: from unknown (HELO apache.org) (stefano@80.105.91.155) by pulse.betaversion.org with SMTP; 25 Mar 2003 11:05:20 -0000 Message-ID: <3E803805.70407@apache.org> Date: Tue, 25 Mar 2003 12:05:41 +0100 From: Stefano Mazzocchi User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: cvs commit: cocoon-2.1 status.xml todo.xml References: In-Reply-To: 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 Stephan Michels wrote: > > On Mon, 24 Mar 2003, Stefano Mazzocchi wrote: > > >>crossley@apache.org wrote: >> >>>crossley 2003/03/22 23:17:16 >>> >>> Modified: . status.xml todo.xml >>> Log: >>> Note about the excellent old functionality to check-jars. >>> >>> Revision Changes Path >>> 1.2 +5 -0 cocoon-2.1/status.xml >>> >>> Index: status.xml >>> =================================================================== >>> RCS file: /home/cvs/cocoon-2.1/status.xml,v >>> retrieving revision 1.1 >>> retrieving revision 1.2 >>> diff -u -r1.1 -r1.2 >>> --- status.xml 21 Mar 2003 13:56:07 -0000 1.1 >>> +++ status.xml 23 Mar 2003 07:17:15 -0000 1.2 >>> @@ -106,6 +106,11 @@ >>> refactoring of samples >>> >>> >>> + >>> + Bring back the check-jars functionality. This verified that all jars >>> + were properly described. It was lost the the recent build re-factoring. >>> + >>> + >>> >>> Move complete Source implementation to Excalibur. >>> >> >>why do we have both todo.xml/changes.xml *and* status.xml? > > > Correct me if I'm wrong. The Forrest project consumes the status.xml file, > and the docs target the todo.xml and changes.xml files. Since we have > decided that we using Forrest for the docs, todo.xml and changes.xml will > be obsolete. aaaah! gotcha. No problem then. Stefano.