DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13042>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13042 Need to have a way to override Java version when parsing ------- Additional Comments From [EMAIL PROTECTED] 2002-09-30 17:46 ------- Oh, sorry. Let me put this more concisely: * There is a JBuilder Ant integration called "AntRunner", which allows us to run Ant from within JBuilder. * JBuilder itself is a Java program that runs on JDK 1.3 (can't run under 1.4 for a variety of reasons). However, the programs that are developed with the IDE are run (and compiled) with whatever JDK I pick (usually JDK 1.4). * The AntRunner extension (which is run within JBuilder itself, and thus uses JDK 1.3) wants to parse the build.xml file, but only to extract the list of targets and descriptions. Once I pick a target to build, it launches an external process (ant.bat) to do this, so the actual build ends up using JDK 1.4. * But because AntRunner itself runs under 1.3, when it parses the build.xml, it gets a bunch of errors about features being unavailable. But these errors are not germane because the actual building itself won't be done under JDK 1.3 - it'll actually happen under JDK 1.4, which is the JDK used by Ant. So the request is for a possible API variant that can pretend to the build.xml parser that the JDK actually is 1.4 (i.e. a variant of parse that says: "please parse this buildfile as if it were going to be executed by a 1.4 JDK". (Of course, it's our responsibility to actually ensure that the build, when it takes place, does so in a 1.4 VM, but that's our problem..) Is this explanation somewhat less confusing? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
