I want a macro to expand to an attribute or not depending on whether the
value is an empty string or not. Suppose I have the following script:
Running macro
I want to optionally include an attribute to the element if the
parameter is given as the non-em
> a) Why do you have "sometimes" the value for mainclass set and sometimes not?
Because sometimes I'm building a DLL and sometimes an executable depending on
whether mainclass is set.
> b) You could use conditional targets ()
But then I'd have to repeat the target twice. I don't want to do tha
I want to optionally include an attribute in a task. Is this possible?
That is, I'm using the csc task and if I'm creating an executable, I
want to include the attribute "mainclass" like
I noticed in Hatcher's properties.xml example file from Java Development
with Ant that he puts a # in front of the comments? What is the reason
for this? Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comm
Antoine Levy-Lambert wrote:
Hello Scott, Dick,
as usual a look at the manual can help. [1]
The answer is to use the fork attribute of the javac task, and specify
the executable.
would do for
instance.
You aren't understanding my problem. Of course I know how to call using
different JDKs. The p
Dick, Brian E. wrote:
There is a java.version property. Maybe you can use that instead of
checking the PATH.
That won't work. I want to use two different JDKs in the same build. The
java.version property just tells me the one it found. This also implies
that I have to spawn the JDK as a separate
We have some Java code that I want to build under multiple JDKs in Ant.
I have both JDK 1.3 and JDK 1.4 installed and I need to build certain
code under each version of the JDK. Any suggestions? I was thinking I
might have to create a custom task to look down the PATH and find the
latest versio