Hello Guy,
from what you are writing, this issue comes from the JDK compiler,
not from ant.
So you should report it to the vendor of the JDK (Sun ?).
If you run ant -verbose, I suppose you can see the classpath used by
ant for compiling.
ant itself will not reject any file from the classpath. The way ant
is written, files with any extension can go in the classpath.
Now it is possible that JDK 1.5.0_10 rejects files with endings other
than jar or zip in compilation classpaths.
Regards,
Antoine
On Feb 25, 2007, at 12:01 PM, Guy Rouillier wrote:
One of our build.xml files includes a SAR (JBoss server archive) in
the
classpath, along with a bunch of other JARs. Up until Java JDK
1.5.0_04
at least, this was working fine. I recently upgraded my
workstation to
1.5.0_10, and now this no longer works. I added verbose="on" to my
javac task, and very clearly, when using JDK 1.5.0_04, the line
"search
path for class files" includes the SAR; when using JDK 1.5.0_10,
the SAR
is not included. All the other JARs are present; it just ignores the
SAR. This is repeatable.
I tried upgrading to Ant 1.7.0 and to the newest available JDK
1.5.0_11,
and still I'm getting the same result. I'm perplexed how the JDK
version can affect the classpath that Ant defines. Unless Ant is
using
some JDK helper class to build up the classpath one JAR at a time, and
that helper class is rejecting the SAR? What options do I have?
Thanks.
--
Guy Rouillier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
