John Collins wrote:
ant
This failed, apparently because base.path means something different at this level than it does in the individual component builds. I'm still confused about his behavior of ant, it seems to be a common problem with multi-level builds.
what happens in the case of excalibur is that the main build file calls buildfiles in subdirectories, "externally". Those buildfiles set the "basedir" directive and other stuff, then call targets inside the main build file "internally". It's a bit of a pain, but it works, sometimes. There's some projects out there with even more complex setups (just look at what we did to get forrest working inside excalibur and you will pull your hair out!); the next generation of tools (maven et al) will make things simpler.
I hope the explanation above gives you the info you needed.
yep!
It's not clear why you have all that stuff in ant.properties.sample; I don't see how it could ever work that way.
lack of maintainance :D
It would be better to use some dummy symbol so ant would complain if it weren't corrected by commenting out or replacing with correct info.
+1. I'll look at it.
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
