On Wed, 15 Jan 2003, Sam Ruby <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote:
>> Log: JVMs >= 1.3 drop CLASSPATH entries that do not exist, so you >> need a <mkdir> for each <work> most of the time. > > Perhaps we should auto-emit a mkdir for each work? Uhm, [bodewig@bodewig project]$ fgrep '<work' *.xml | fgrep .jar jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_core.jar"/> jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_components.jar"/> jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_functions.jar"/> jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_http.jar"/> jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_ftp.jar"/> jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_jdbc.jar"/> jakarta-jmeter.xml: <work nested="lib/ext/ApacheJMeter_java.jar"/> jakarta-taglibs.xml: <work nested="dist/standard/lib/jstl.jar"/> jakarta-taglibs.xml: <work nested="dist/standard/lib/standard.jar"/> jakarta-velocity.xml: <work nested="test/cpload/test1.jar"/> jakarta-velocity.xml: <work nested="test/cpload/test2.jar"/> jakarta-velocity.xml: <work nested="test/multiloader/test1.jar"/> jakarta-velocity.xml: <work nested="test/texen-classpath/test.jar"/> xml-axis.xml: <work nested="java/build/lib/axis-ant.jar"/> xml-soap.xml: <work nested="java/build/lib/soap.jar"/> better not ;-) I'm pretty sure that each of these jars exists before we'd come to the mkdir command (otherwise these <work> tags don't do anything anyway), but one never knows. > If a profile did include jakarta-ant.xml, however, the <home > nested="dist"> element in jakarta-ant.xml would indicate a directory > which had a layout quite similar to an installed package. I see. With this, <javadoc> would better use <home> (it doesn't) and <work> may or may not as it doesn't have any relevance for "outside" projects IMHO. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
