On Tue, 23 Mar 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
I'll simply try whether meta-sourceresolve builds without fortress-tools to see whether it is unneeded here as well.
I think I need your help here, Stephen.
excalibur-sourceresolve and excalibur-meta-sourceresolve compile the same classes using the same build file and target and claim to produce exactly the same jars. They only differ in their stated dependencies.
Are they the same project? If so, we should probably drop meta-sourceresolve.
In "traditional" Gump, excalibur-xmlutils builds since Gump finds the jar produced by excalibur-sourceresolve. Python Gump on the other hand "knows" that excalibur-meta-sourceresolve hasn't been built and this causes the pre-req failures upstream.
It turns out that xmlutils compiles just fine against the jar created by excalibur-sourceresolve - and so would Cocoon. I'm puzzled.
Right now I'd probably replace excalibur-meta-sourceresolve with excalibur-sourceresolve all over the place.
+1
We were thinking the same thing. I'm cc'ing [EMAIL PROTECTED] just for reference.
Cheers, Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
