Hi John,
just to be clear, you did a
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co \ avalon-excalibur avalon avalon-logkit
Yes.
cd avalon-logkit ant
Yes, but I didn't have some of the libraries it wanted, so I used a downloaded jar for the excalibur build.
cd ../avalon ant
Yes.
cd ../avalon-excalibur
Looked at the build.xml and ant.properties.sample, and decided I wanted to tell it where to find junit and the downloaded logkit jar. So I copied ant.properties.sample to ant.properties and added those two locations. I didn't touch any of the rest of it, it seemed reasonable.
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. After I commented out all of ant.properties except my outboard versions of junit and logkit.jar, it builds fine. It took a few runs of ant -verbose to see what was happening.
(or equivalent with other commands) and that didn't work? It works on my end...could you please rename your ~/.ant.properties and /avalon/**/ant.properties to something else, and send in the output of
'ant clean; ant -v' (ie verbose output)?
I hope the explanation above gives you the info you needed. 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. 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.
John Collins University of Minnesota
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
