Hi,
I currently don't understand why Gump on LSD thinks Cocoon would
depend on avalon-fortress-container, but the Gump instance on
covalent.net tries to build it[1].
The build fails since Cocoon only states a dependency on the
avalon-framework API but uses implementation classes as well[2].
The appended patch should fix that.
Cheers
Stefan
Footnotes:
[1] http://gump.covalent.net/log/cocoon.html
[2] http://marc.theaimsgroup.com/?l=avalon-dev&m=107961713821764&w=2
--
http://stefanbodewig.blogger.de/
Index: gump.xml
===================================================================
RCS file: /home/cvspublic/cocoon-2.1/gump.xml,v
retrieving revision 1.127
diff -u -r1.127 gump.xml
--- gump.xml 20 Mar 2004 01:50:59 -0000 1.127
+++ gump.xml 23 Mar 2004 07:27:44 -0000
@@ -38,7 +38,7 @@
<ant target="gump-core">
<property name="version" value="@@DATE@@"/>
<depend property="logkit.jar" project="dist-avalon-logkit"/>
- <depend property="avalonapi.jar" project="avalon"/>
+ <depend property="avalonapi.jar" project="avalon-framework" id="api"/>
</ant>
<depend project="ant" inherit="runtime"/>
@@ -47,6 +47,7 @@
<depend project="xml-xalan2"/>
<depend project="xml-commons-resolver"/>
+ <depend project="avalon-framework" ids="impl"/>
<depend project="excalibur-compatibility"/>
<depend project="excalibur-instrument"/>
<depend project="excalibur-instrument-manager"/>
