You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Ed Mack <ed...@wrq.com> on 2002/08/08 01:59:57 UTC

Mixing compilers

Hello,
I'm running Ant 1.5 under the 1.4.0_01 JDK and I need to compile some 1.1
classes, but I get errors from my compile target:
 
    [javac]
D:\EnterView\5.1\source\com\wrq\enterview\deploy\convert\SessionUpgr
ade.java:282: warning: as of release 1.4, assert is a keyword, and may not
be us
ed as an identifier
 
My (simplified) 1.1 javac target is as follows:
 
 <javac
      target="1.1"
      fork="yes"
      srcdir="${preproc_dir}"
      destdir="${obj_dir}"
      bootclasspath="${tools_dir}/jdk-1.1/lib/classes.zip"
      classpath="${preproc_dir}:${1.1-jars}"
 />

Another piece of info (maybe it's related).  I also get the "[javac] Since
fork is true, ignoring compiler setting."
message.  (What is being ignored?!)
 
Can someone help?!  This worked using the 1.3.1 JDK, even without the
"bootclasspath" option.
 
Thanks,
Ed
 

Ed Mack
Mgr, Configuration Developers & Release Engineers
WRQ, Inc.
206.217.7469
 <ma...@wrq.com> edm@wrq.com

  <http://www.wrq.com/images/signature_logo.gif>  


WRQ has 21 years of experience providing integration software and services
for host-intensive environments. To learn more about our Reflection and
Verastream products, visit  <http://www.wrq.com/products/>
http://www.wrq.com/products/.



 

Re: Mixing compilers

Posted by "Hal Hildebrand (web)" <Ha...@hellblazer.com>.
I think all you should need to do is add the "source" attribute:

  <javac
       source="1.3"
       target="1.1"
       fork="yes"
       srcdir="${preproc_dir}"
       destdir="${obj_dir}"
       bootclasspath="${tools_dir}/jdk-1.1/lib/classes.zip"
       classpath="${preproc_dir}:${1.1-jars}"
  />

Technically, 1.3 is the default so this shouldn't be necessary.  Some
helpful something seems to be overriding this...

----- Original Message -----
From: "Jacob Kjome" <ho...@visi.com>


> Yep,
>
> Read the j2sdk1.4 release notes.  The one bit of backward
compatibility
> that they broke was in the assert syntax.   As far as the javac
message,
> why are you forking?  If you fork, you move into a separate JVM
process
> where, I imagine, the special Ant build.compiler "magic" properties
don't
> apply.  The fix?  Don't fork javac.
>
> Jake
>
> At 04:59 PM 8/7/2002 -0700, you wrote:
> >Hello,
> >I'm running Ant 1.5 under the 1.4.0_01 JDK and I need to compile some
1.1
> >classes, but I get errors from my compile target:
> >
> >     [javac]
> >D:\EnterView\5.1\source\com\wrq\enterview\deploy\convert\SessionUpgr
> >ade.java:282: warning: as of release 1.4, assert is a keyword, and
may not
> >be us
> >ed as an identifier
> >
> >My (simplified) 1.1 javac target is as follows:
> >
> >  <javac
> >       target="1.1"
> >       fork="yes"
> >       srcdir="${preproc_dir}"
> >       destdir="${obj_dir}"
> >       bootclasspath="${tools_dir}/jdk-1.1/lib/classes.zip"
> >       classpath="${preproc_dir}:${1.1-jars}"
> >  />
> >
> >Another piece of info (maybe it's related).  I also get the "[javac]
Since
> >fork is true, ignoring compiler setting."
> >message.  (What is being ignored?!)
> >
> >Can someone help?!  This worked using the 1.3.1 JDK, even without the
> >"bootclasspath" option.
> >
> >Thanks,
> >Ed
> >
> >
> >Ed Mack
> >Mgr, Configuration Developers & Release Engineers
> >WRQ, Inc.
> >206.217.7469
> >  <ma...@wrq.com> edm@wrq.com
> >
> >   <http://www.wrq.com/images/signature_logo.gif>
> >
> >
> >WRQ has 21 years of experience providing integration software and
services
> >for host-intensive environments. To learn more about our Reflection
and
> >Verastream products, visit  <http://www.wrq.com/products/>
> >http://www.wrq.com/products/.
> >
> >
> >
> >
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Mixing compilers

Posted by Jacob Kjome <ho...@visi.com>.
Yep,

Read the j2sdk1.4 release notes.  The one bit of backward compatibility 
that they broke was in the assert syntax.   As far as the javac message, 
why are you forking?  If you fork, you move into a separate JVM process 
where, I imagine, the special Ant build.compiler "magic" properties don't 
apply.  The fix?  Don't fork javac.

Jake

At 04:59 PM 8/7/2002 -0700, you wrote:
>Hello,
>I'm running Ant 1.5 under the 1.4.0_01 JDK and I need to compile some 1.1
>classes, but I get errors from my compile target:
>
>     [javac]
>D:\EnterView\5.1\source\com\wrq\enterview\deploy\convert\SessionUpgr
>ade.java:282: warning: as of release 1.4, assert is a keyword, and may not
>be us
>ed as an identifier
>
>My (simplified) 1.1 javac target is as follows:
>
>  <javac
>       target="1.1"
>       fork="yes"
>       srcdir="${preproc_dir}"
>       destdir="${obj_dir}"
>       bootclasspath="${tools_dir}/jdk-1.1/lib/classes.zip"
>       classpath="${preproc_dir}:${1.1-jars}"
>  />
>
>Another piece of info (maybe it's related).  I also get the "[javac] Since
>fork is true, ignoring compiler setting."
>message.  (What is being ignored?!)
>
>Can someone help?!  This worked using the 1.3.1 JDK, even without the
>"bootclasspath" option.
>
>Thanks,
>Ed
>
>
>Ed Mack
>Mgr, Configuration Developers & Release Engineers
>WRQ, Inc.
>206.217.7469
>  <ma...@wrq.com> edm@wrq.com
>
>   <http://www.wrq.com/images/signature_logo.gif>
>
>
>WRQ has 21 years of experience providing integration software and services
>for host-intensive environments. To learn more about our Reflection and
>Verastream products, visit  <http://www.wrq.com/products/>
>http://www.wrq.com/products/.
>
>
>
>