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: Extending the build system for modules
Date Thu, 15 Aug 2002 08:03:23 GMT
Geoff Howard wrote:
> Currently, the method for building without fop, or any other optional 
> "module" is to remove jars from the lib/optional directory.  This is 
> fine the first time you build, but they are replaced on every cvs 
> update requiring moving/deleting them again.  For anyone trying to 
> keep up with HEAD, that means a lot of going back and figuring out 
> which jars you don't need each time.  Since the first step in 
> debugging a problem is often "make sure you have the latest version 
> of HEAD" this can be a real PITB.
> 
> The same is true of xconf, and sitemap.  I would want to be able to 
> upgrade the core of cocoon, or any needed modules without having to 
> manually edit xconf (currently we've added a database resource, a custom 
> component, configured the stores, etc. in xconf) or the sitemap.
> 
> Am I adequately painting a picture of the problem?  
> 
Yes, and exactly this should be solved with the new build system - because
you don't need to remove jars from the optional directory anymore.

Carsten

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


Mime
View raw message