Or if you have a fixed number of machines where builds can take place you can simply make the properties machine specific, something like this
[properties file=some.properties] machine1.jdk.1.3.location=c:\\java\\ .... machine2.jdk.1.3.location=d:\\java\\ .... etc
[build file] ... <property environment="env"/> <property file="some.properties"/>
# this is in ant-contrib if you are not familiar with it
<propertycopy name="jdk1.3.location" from="${env.HOSTNAME}.jdk1.3.location"/>
...
This will pick up the property for the specific machine running the build and put it in jdk.1.3.location.
In my opinion looking down the path for jdk locations is probably not the best thing to do.
But this is just my opinion
Good Luck
Doug Lochart
Ace Technologies Inc.
Scott Simpson wrote:
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.
<javac fork="true" executable="c:/jdk1.3/bin/javac.exe"/> would do for instance.
You aren't understanding my problem. Of course I know how to call using different JDKs. The problem is finding these JDKs on the path in the first place. I want to find the JDKs on the path and pick the latest ones for 1.3, 1.4, etc.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]