Peter,
nope - the problem is the build file writer ;)
Swine ;-)
in that when antcall is invoked all relative pathelements should be corrected.
Impossible to do because there is no way to type values. That is why <property/> supports the location attribute (which resolves to absolute filename) however the user must explicitly use this.
Learn something new every day.
OK, Catalina's build forces the existance of build.properties and a template is provided. It does not offer much by way of textual help, but few downloads and assigments the build will work. I am not sure it is perfect as the unless="" help does not give much explanation. For the case above, xerces.jar is needed for some blocks. It could be in one of three places :In that world we'd be fine, but build must work for people who have downloaded source and not got from CVS. I think perhaps we should lean on ant.properties more and <echo>warnings</echo> if ant.properties indicated paths are missing. i.e. Force the builder thru a few iterations of setting up the env, before a successful build.
Sorta sounds like a good idea. Can yoiu expand?
1) ../../jakarta-avalon/tools/lib/xerces.jar (cornersone, logkit, excalibur etc via CVS)
2) ../../../../jakarta-avalon/tools/lib/xerces.jar (demo, bay, ftpserver & jesktop via CVS)
3) ${ANT_HOME}/lib/xerces.jar
4) ${AVALON_TOOLS}/lib/xerces.jar
It all depends on whther you've CVSed or downloaded and if ou CVSed, did you put the project roots in the same dir..
Perhaps we could specify the full path in ant.properties (or build.properties like Catalina) and give extensive help if dependancies are not satisfied during some pre-compilation step.
Regards,
- Paul H
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
