> 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].
I wonder if the removal of the 'full dependencies' and 'full dependees' tables (on 'working projects') is a good thing or not. It might be nice in this case. It seems to me that cocoon depends upon xmlutil: http://lsd.student.utwente.nl/gump/cocoon-2.1/cocoon.html#Project+Dependenci es and excalibur-xmlutil depends upon avalon-fortress-container: http://lsd.student.utwente.nl/gump/avalon-excalibur/excalibur-xmlutil.html ... however (unfortunately) without the full depends information the trail goes somewhat cold. Luckily we can follow the pre-req fails: excalibur-meta-sourceresolve avalon-fortress-tools avalon-fortress-container We need a nicer way to determine this path. Looking at this list I see the dependency is runtime, not compile time. I'm not awake enough to determine if it is misguided (or not) to set this as pre-requisite failed or not. Thoughts? regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
