cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <tcu...@apache.org>
Subject Re: gump libraries etc
Date Mon, 07 Feb 2005 11:03:44 GMT
Hey Torsten! (be friendly when you are talking to yourself ;)

In the build/cocoon-2.2.0-dev/temp/blocks-build.xml I found

<target unless="internal.exclude.block.javaflow"
name="cocoon-block-javaflow-lib" depends="cocoon-block-javaflow">
<copy todir="${build.webapp.lib}" filtering="off">
<fileset dir="${lib.optional}">
<include name="javaflow*.jar"/>
<include name="jci*.jar"/>
</fileset>
</copy>
<block-lib dir="src/blocks/javaflow" name="javaflow"/>
</target>
<target unless="internal.exclude.block.javaflow"
name="cocoon-block-javaflow-prepare" depends="cocoon-block-javaflow">
<mkdir dir="${build.blocks}/javaflow/dest"/>
<path id="javaflow.classpath">
<path refid="classpath"/>
<fileset dir="${lib.optional}">
<include name="javaflow*.jar"/>
<include name="jci*.jar"/>
</fileset>
<fileset dir="src/blocks/javaflow">
<include name="lib/*.jar"/>
</fileset>


So src/blocks-build.xsl seems to create

  javaflow*.jar
  jci*.jar

which is because of the gump project names.

So always make sure the gump project names
correspond to the jar names ...or fix it ;)

cheers
--
Torsten

Mime
View raw message