https://issues.apache.org/bugzilla/show_bug.cgi?id=50678
--- Comment #4 from Antoine Levy-Lambert <[email protected]> 2011-01-31 16:28:04 EST --- Ant's classloaders used by <taskdef/> are not able to add to the startup classpath of Ant or of the JVM, and this limitation is a problem in the case of some JVM factories which do not see children classloaders. You can use the classloader task documented at http://enitsys.sourceforge.net/ant-classloadertask/usage.html to add jars (for instance xercesImpl and xml-apis) to the appropriate classloader. I am maintaining a build file where we need to put a number of jars on a classloader above the taskdefs classloader. Here is how I do it with the enitsys classloader task : <classloadertask classpathRef="all.https.cp" loader="thread"/> I use this task also to put mail.jar/activation.jar on the classpath when I need to send email from a build file using the functionality supplied by these. I am tempted to close your bug report as WONTFIX but it is one more indication that there are lots of usages in the field for this <classloadertask/> so we should integrate it in Ant if it is technically and procedurally acceptable for the project. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
