> From: Conor MacNeill [mailto:[EMAIL PROTECTED] > > From: Dominique Devienne [mailto:[EMAIL PROTECTED] > > > > Before Ant 1.6 releases officially, I'd like to propose that the new Ant > > launcher automatically recognizes a non-empty ant/lib/endorsed > directory, > > and sets/augments the appropriate Java system property. > > > > This will avoid folks like me to put Xalan in ant/lib, and not > > have it fully > > used when running <style> or <junitreport>. Thanks, --DD > > > > If we are to have an endorsed dir, should it not also apply to Ant's own > VM?
Yes, that's what I meant. I guess I muddied the point by talking about the new Launcher, didn't I! Since I'd like the XML-transform related tasks to properly use the supplied Xalan when running under JDK 1.4+, it is Ant's own VM that should get the java.endorsed.dirs Java system property set. That implies this being done at ant.bat/sh I'm afraid. If it's not in Ant 1.6, I'll do it in my own copy of Ant, but I think it's generally useful. Something else to think about would be to pass down these special Java system properties used by Ant's VM down to forked VM's. I'm not sure this is done currently. There's java.endorsed.dirs, but also java.ext.dirs, and java.library.path, and the logging properties, and in general all those properties that must be set at VM startup. Does Ant pass down its own VM's Java System properties to the forked VM? I think it probably should if it doesn't already, with an attribute to disable it maybe. Does the 'newEnvironment' attribute apply to both the env. vars *and* the Java System properties? Thanks, --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
