Thanks. This is a common build script that we have, so I didn't add fork for the javac task - as it would affect other builds as well, that use the latest java version and follow the default build.
If it is not possible at all to incorporate something in the common build, I will take a look at separating this one out, but want to avoid it, if I can. I had looked at the endorsed directory, but I got the impression that it is to be used when you want to use a later version, not earlier. Is that not true? Also, if I can use it for earlier version, can I use the JAXB jars from the WEB-INF/lib directory for the path for - Djava.endorsed.dirs=/relative-path-to/WEB-INF/lib? Would other jars in that location cause any issues for endorsed directory? -----Original Message----- From: Dominique Devienne [mailto:ddevie...@gmail.com] Sent: Monday, September 15, 2014 11:30 AM To: Ant Users List Subject: Re: Need help with ANT javac classpath On Mon, Sep 15, 2014 at 5:15 PM, WebServices Development < webservices_developm...@csx.com> wrote: > P.S - I tried adding includejavaruntime="false" and > includeantruntime="false" attributes - both together as well as > individually - to the javac task - but I still get the error. The > error is - createBinder() in ObjectFactory cannot override > createBinder() in JAXBContext > Did you fork="true" too, for <javac>? That way you can have better control of the environment the JDK javac (implemented in Java) runs with, separate the from environment Ant itself runs in. Also look into http://docs.oracle.com/javase/6/docs/technotes/guides/standards/ A quick Google also turned up http://stackoverflow.com/questions/16215409/is-it-possible-to-replace-the-version-of-the-jaxb-implementation-in-java-jre-1-6 --DD This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email.
