Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <46D2D718.20308@apache.org>
Date: Mon, 27 Aug 2007 15:52:24 +0200
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Splitting and cleaning up cocoon-core
References: <46D2C915.7060500@apache.org> <46D2D127.4090900@apache.org>
In-Reply-To: <46D2D127.4090900@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Grzegorz Kossakowski wrote:
> Reinhard Poetz pisze:
>> * I will change my opinion if cocoon-core doesn't contain Java code
>> anymore and everything is at its right place ...
> 
> I've taking a look on this issue when working on GSoC and moving stuff around. Basically we have:
> 
>   * code that can be moved immediately because there is no problem with dependencies
> 
>   * code that has some very complicated dependencies like CocoonSourceResolver
> 
>   * code that itself does not have any problems with dependencies but its tests depend on code from
> cocoon-core like CocoonTestCase. We can get rid of CocoonTestCase reliably only switching from
> Avalon to Spring so our components become beans thus much more test-friendly.
> 
> We could think about spending some time on it at Hackathon, WDYT?

yes, we should come up with a task list. The actual work should happen aftwards 
because we shouldn't break Cocoon (too often) while so many people will be 
working on it.

-- 
Reinhard P�tz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------