Costin Manolache wrote:
Actually, the problem was that the "bin" directory was set as endorsed, and one JAR in there was including a lot of things that didn't belong. Nasty bug to spot ;-)It won't happen in JDK1.3It won't happen if you remove the "endorsed.dirs" from the CLI. I think endorsed is completely broken, there are many other problems and leads to undeterministic behavior. We should just remove it and add it back in JDK1.5 or when it is fixed.
This should fix all the commons-logging CL failures users have been reporting (I think).
With only the XML parser in there, I don't think it creates problems. If the user tries to use it, there could be problems, that's true ;-) It's a bit like allowing users to change the system classpath, actually.My +1 to remove the "endorsed". There is no need to use a different version of javax.xml or org.w3c.dom or org.xml - and if someone needs a different one, he can use JDK1.3 or file a bug report on Sun site.
BTW, I'm having issues with your latest change to the main build.xml (it fails trying to build Coyote).
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
