Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4177BDB5.8070706@reverycodes.com>
Date: Thu, 21 Oct 2004 09:46:29 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [cron block] dependency question
References: <HAI01IM9QX2CTp2hFOW00000841@hai01.hippo.local>
 <4177AB62.3020508@hippo.nl>
In-Reply-To: <4177AB62.3020508@hippo.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Unico Hommes wrote:
> 
> What 
> about having only one repository location for blocks? I am so tired of 
> all the duplicate effort we have to do for each and every change to 
> blocks. It shouldn't be neccessary.
> 
> There probably isn't a small amount of work involved to get it working 

Me thinks it is enough to change just one line in build.properties?

   blocks=${src}${file.separator}blocks


> but I'd like to know exactly what it would take to byte this bullet. 
> Some of the steps involved that I can distinguish are:
> 
> 1. Merge/sync the current 2.1.x and 2.2 blocks.What blocks have the 
> biggest differences between their 2.1.x and 2.2 copy?

svn diff


> If there are 
> unresolvable differerences, how to handle that?

Before we start to speculate, we should identify such differences and discuss 
them. If 2.2 to be compatible with 2.1 (modulo deprecations), blocks should not 
have unresolvable differences.

Vadim