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
--------------------------------------------------------------------
