Hi Brett, Brett Porter wrote on Thursday, August 04, 2005 4:21 PM:
> On 8/4/05, Derek Lane <[EMAIL PROTECTED]> wrote: >> In my case, I have specified to the 1.4 compiler that I want it to >> generate code that will run in a 1.3 JVM. How am I doing so far? > > Correct. > >> A) In some circumstances, based on the specific 1.3 runtime JVM, the >> code generated by the 1.4 compiler will not successfully run? > > Yep. It's not the JVM that is the problem, but the runtime > class libraries (rt.jar). > > The most prevalent example: > http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/2 >00506.mbox/[EMAIL PROTECTED] >if you append a stringbuffer, the code compiles in both 1.4 and 1.3, >but when compiled on 1.4 it won't run on 1.3 (because append >StringBuffer doesn't exist), unless you cast to (Object). Isn't it enough to set also the bootclasspath? For M1 I set: maven.compile.fork=yes maven.compile.target=1.3 maven.compile.compiler=javac1.3 maven.compile.executable=${jdk13.home}/bin/javac maven.compile.compilerargs=-bootclasspath ${jdk13.home}/jre/lib/rt.jar maven.junit.fork=true maven.junit.jvm=${jdk13.home}/jre/bin/java - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
