Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Tue, 19 Aug 2003 19:58:25 +0200
Subject: Re: Config File Proposal (was... sort of...: [ANN] Apache Cocoon 2.1
 Released - binary??)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Stefano Mazzocchi <stefano@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <03da01c36449$f3c43c20$fb590644@cruiser>
Message-Id: <BAED4466-D26E-11D7-BC60-000393D2CB02@apache.org>


On Sunday, Aug 17, 2003, at 00:58 Europe/Rome, Jay Freeman ((saurik)) 
wrote:

> The #1 thing that would help me start using Cocoon is orthogonal to a
> binary/source distribution issue (and I'll note my preference is 
> towards
> binary on this axis).
>
> I agree with you (and the previous arguments, I read through the entire
> thread that was linked to) that taking Cocoon and getting it into a 
> state
> where I can start making changes to it is one of the most irritating 
> steps
> to getting Cocoon working. However, 2.1 hasn't changed this all that
> terribly much. (If you look at this e-mail and go "oh, he doesn't know 
> how
> to use the build environment", please skip to "[START HERE]" later in 
> the
> post before making a snap judgement on my point. If you want to just 
> see
> what I'm proposing, skip to [PROPOSAL], although that skips part of the
> explanation of "why?".)

Have you read the "Cocoon Block" design RT?

--
Stefano.