On Mon, Jan 14, 2002 at 06:37:17PM +1100, dion wrote: > Before I go and submit a patch for these problems can someone else > verify I'm not going crazy? > > The jakarta-commons/build.xml does NOT reference build.properties, even > though there is a build.properties.sample in the same directory, with > instructions on how to use it. > > The file the build.xml is looking for is actually .ant.properties
Hm. IIRC, some projects' build.xmls did assume that common jars (like junit.jar) were defined in "../build.properties". Maybe that's changed. The whole thing is getting a bit messy. I posted a patch a while ago, but it wasn't applied: http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=100337787122376&w=2 > Also, when attempting to run build.xml, velocity appears to have > introduced a dependency on org.apache.log.output.AbstractOutputTarget > that isn't declared in the build file, and Anakia fails with a > NoClassDefFoundError. > > My proposed steps are: > - rename the project specific .ant.properties in the build.xml to > build.properties > - add the logKit jar file to the build.properties.sample and the build.xml Should we assume developers have downloaded velocity, or jakarta-site2 (which httpclient assumes)? If jakarta-site2, we can just have velocity.jar defined, because it includes the logkit jars. --Jeff > Please tell me I've got it wrong! > -- > dIon Gillard, Multitask Consulting > http://www.multitask.com.au/developers > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
