cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: [proposal] aiming to a naked cocoon
Date Wed, 12 Feb 2003 09:25:12 GMT


Bertrand Delacretaz wrote, On 12/02/2003 10.20:
> Le Mercredi, 12 fév 2003, à 10:12 Europe/Zurich, Stephan Michels a écrit :
> 
>> ...
>> +1, especially moving the libs into the blocks...
> 
> 
> Wouldn't the duplication of jars generate a huuuuuge CVS repository? 
> It's big enough already.
> 
> An option might be to keep the jars in a well-structured lib/ 
> subdirectory and have the block's build.xml copy the required jars to 
> its workspace before compiling. Easy to do with ant filtered copy task.
> 
> The lib/ could then include "version directories" if different versions 
> of jars are needed for different blocks (at compile time - I know it's 
> going to be a problem at runtime):
> 
>   lib/fop/0.20.1/fop-0.20.1.jar
>   lib/fop/0.20.4/fop-0.20.4.jar
>   lib/fop/0.20.4/some-additional-jar-for-0.20.4.jar
> 
> And then each block pulls what it needs from this tree.

Krysalis Ruper can already get Jars from a remote repository, and it's 
an Ant task. IF we decide that we want to keep the repository in the 
Cocoon CSV, it can already do the above and "synch" with that.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


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


Mime
View raw message