According to the Ant 1.8.4 docs, wildcards are only supported in the
'location' attribute of a pathelement or a classpath. Based on this,
your classpath element should be:
Maury
On 01/15/13 15:38, WebServices Development wrote:
Sorry, there was a typo on javac call classpath. I
Thank you. I presume this is answer to my first question - Which javac does
ant use? Is it in the ANT code that doesn't process the wildcard classpath? Is
this javac class a java compiler class, or just a class that defines ANT's
javac task ? If it is a compiler, then does it mean that ANT's
you will find a javac key in
.\org\apache\ant\taskdefs\default.propertiesjavac=org.apache.tools.ant.taskdefs.Javac
defaults.properties is wholly contained within ant.jar inside
$ANT_HOME\lib\ant.jar
Martin
__
Verzicht und Vertraulichkeitanmerkung/No
Sorry, there was a typo on javac call classpath. It should have been
JAVA_HOME=/opt/local/software/websphere/v7/java/bin
export JAVA_HOME
JDK_HOME=/opt/local/software/websphere/v7/java
export JDK_HOME
/opt/local/software/websphere/v7/java/bin/javac -verbose -d
/home/ab/antcode/build/classes -cla
Actually, currently I am testing with hardcoding the classpath as in below task
definition. I ultimately want to create a classpath from a string, but that is
next question, if I can get this working. This is the same path I am using in
my commandline javac call
Without knowing how you are creating the classpath for ant to use, it is
impossible to say why it is not working for you. It may be something as
simple as using the wildcard in a way that has ant expanding it rather
than it being passed through to javac.
Maury
On 01/14/13 17:23, WebServices
