cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [CLEANCOON] Let's clean Cocoon and modularize it (was: Cocoon Organization (Cocoon plugins))
Date Tue, 06 Aug 2002 07:04:33 GMT
+5

Carsten

> -----Original Message-----
> From: Christian Haul [mailto:haul@dvs1.informatik.tu-darmstadt.de]
> Sent: Tuesday, August 06, 2002 8:59 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [CLEANCOON] Let's clean Cocoon and modularize it (was:
> Cocoon Organization (Cocoon plugins))
> 
> 
> On 06.Aug.2002 -- 08:32 AM, Carsten Ziegeler wrote:
> > So, *if* we vote on refactoring or starting a new Cocoon
> > major version, I'm definitly -1 on this. 
> > 
> > I still believe that we can solve some (perhaps not all)
> > problems simply by organizing our project structure and
> > by shifting our activities from "hacking new features"
> > to "making a more perfect solution".
> 
> So, could we just come back to Berin's original idea, create some
> subdirectories based e.g. on functionality, move stuff to
> subdirectories if appropriate, and change the build process to include
> these subdirectories as we do with scratchpad?
> 
> Step two could be to build seperate jars, step three to relax release
> cycles for sub-projects. No magic, no changing of any names, just
> re-packaging. 
> 
> Candidates so far:
> 
> * forms (simple and XML)
> * databases (esql, transformer, actions)
> * fop
> * portal
> 
> How about (in addition to the above):
> 
> * delhi
> * docbook
> * ...
> 
> Thus I suggest that someone more knowledgeable of the build process
> creates directories for the above and integrates them with the process
> and then those who feel responsible for components move them and their
> samples to one of the subprojects where sensible.
> 
> Step four could be to make this pluggable, i.e. blocks.
> 
> 	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
> 

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


Mime
View raw message