cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: cvs commit: cocoon-2.1
Date Mon, 08 Sep 2003 20:10:54 GMT
Hmm, I'm not satisfied with the answer :-)

Carsten has added a depend functionality to the gump descriptor and 
blocks-build.xsl. I.e. the user does not need to care and to know about 
the dependencies. The dependencies are handled completely automatically 
- at least I hope so; from a short look on the changes to 
blocks-build.xsl I also think it does this. There is for example 
following entry in the gump.xml:

   <project name="cocoon-block-scratchpad">

     <ant target="gump-block">
       <property name="block-name" value="scratchpad"/>
       <property name="version" value="@@DATE@@"/>

     <depend project="cocoon" inherit="all"/>
     <depend project="castor"/>
     <depend project="commons-jexl" inherit="all"/>
     <depend project="jakarta-velocity" inherit="all"/>
     <depend project="jakarta-servletapi-4"/>
     <depend project="cocoon-block-velocity"/>
     <depend project="cocoon-block-cron"/>

     <work nested="tools/anttasks"/>
     <home nested="build/cocoon-@@DATE@@"/>

     <jar name="blocks/scratchpad-block.jar"/>

     <nag from="Gump" to=""/>

and so the dependency on the cron block. The same is true for portal 
block depending on the html block (because of JTidy).


Bertrand Delacretaz wrote:
> Le Dimanche, 7 sep 2003, à 13:36 Europe/Zurich, Joerg Heinicke a écrit :
>> ...Isn't this now handled by the dependency in the gump descriptor? At 
>> least I read something about library dependency on blocks (portal vs. 
>> html). So do we need this comments in the properties files? Especially 
>> for FOP it's only a dependency on the batik library....
> There are indeed dependencies between blocks at compile time - disabling 
> the cron block, for example, prevents the scratchpad block from compiling.
> -Bertrand

View raw message