Firstly, apologies if this seems off list: the general point might be better addressed to the user list, but I have an issue with the "javac" task's default value for the "executable" attribute and the "junit" task's default value for the "jvm" attribute that probably relates better to this list.
I've been looking at how to run Ant using 1.4 (we have Ant tasks that use 1.4 specific features) while have it use a 1.3 compiler for the "javac" task (and 1.3 runtime for "junit" test execution task). We need to do this to ensure that our developed software is 1.3 compatible. I *had* assumed that all I needed to do was set JAVACMD to point to the 1.4 java executable and have JAVA_HOME point to a 1.3 JDK. Sadly, this doesn't appear to be the case. I don't understand why the "javac" task requires the "executable" attribute to be specified when attempting to do this (the documentation says it defaults to the compiler for the JDK that Ant is run by... surely this *should* default to the one found in JAVA_HOME instead). I assume that I will have to explicitly use the "jvm" attribute on the "junit" task invocation (again, it would seem sensible if this task used JAVA_HOME to resolve the executable by default). What do people think about the defaults for javac executable and junit jvm? Has anyone tried to do this sort of thing (different Ant and javac/junit Javas)? If so, any hints or tips welcome! Phil :n. -- Phil Weighill-Smith <[EMAIL PROTECTED]> Volantis Systems
