cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <h...@dvs1.informatik.tu-darmstadt.de>
Subject Re: [CLEANCOON] Let's clean Cocoon and modularize it (was: Cocoon Organization (Cocoon plugins))
Date Tue, 06 Aug 2002 07:56:52 GMT
On 06.Aug.2002 -- 09:48 AM, Torsten Curdt wrote:
> <snip/>
> 
> > I would suggest something like this:
> >
> > Core:
> > src/java/org/apache/cocoon/*
> >
> > FOP module:
> > src/modules/fop/build.xml
> > src/modules/fop/lib/*
> > src/modules/fop/java/org/apache/cocoon/serialization/*
> > src/modules/fop/java/org/apache/cocoon/components/*
> > src/modules/fop/samples/*

Just one minor point: we have already "components", "parts", and
"modules". We need yet another term for this. "block" is too much
associated with a much richer implementation although this might
evolve into "blocks".

But yes, we should keep the original package names and thus the
original directory structure.

Another point: This this won't break anything, we could do it for
2.0.4 as well and "mv" (unix: move) the files on
cvs.apache.org. Loosing cvs logs is a pitty and should be avoided.

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message