Simon, Thanks for the explanation. For now it seems we will have to settle for the limited 1.3 compatability.
Sean On 3/7/06, Simon Kitching <[EMAIL PROTECTED]> wrote: > Hi, > > The manifest JVM version is whatever JVM was used to run the "jar" task, > which obviously *was* the 1.4 jvm. > > I expect that the <source> and <target> tags just set the -source and > -target options for the compiler. So the compiler used is still the > default one (whatever was used to run maven; 1.4 in this case), but it > has been told to generate bytecode compatible with 1.3 JVMs. > > There are some problems with just using <target> though. The java > compiler still uses the *current rt.jar* libraries even though it > outputs old-format bytecode. Code that references classes/methods not in > the older java version will therefore compile but not run on the target > JVM. In addition, there are a few corner cases where new overloaded > methods have been added to the library, causing code which compiles > *successfully* with (eg) javac-1.3 AND javac-1.4 to fail when the > 1.4-compiled version is run in a 1.3 JVM. One of the StringBuffer > methods falls into this category. > > Unfortunately, Maven2 requires java 1.4 to run, so simply running the > whole build with java 1.3 won't work. I did see some stuff in the maven > docs about specifying a *path to a jdk* in the maven-compiler-plugin > configuration. > > Cheers, > > Simon > > On Tue, 2006-03-07 at 20:56 +0000, Dennis Byrne wrote: > > Weird, the manifest said jdk 1.4 though. > > > > Dennis Byrne > > > > >-----Original Message----- > > >From: Sean Schofield [mailto:[EMAIL PROTECTED] > > >Sent: Tuesday, March 7, 2006 03:37 PM > > >To: 'MyFaces Development' > > >Subject: Re: Core and JDK 1.3 > > > > > >I believe the core is already compiled using: > > > > > > <plugins> > > > <plugin> > > > <artifactId>maven-compiler-plugin</artifactId> > > > <configuration> > > > <source>1.3</source> > > > <target>1.3</target> > > > </configuration> > > > </plugin> > > > </plugins> > > > > > >This plugin is configured in the master pom. I have "released" > > >myfaces-maven-1.0.1 but I'm not going to have the maven guys push it > > >to ibiblio until we are ready to push shared and core. > > > > > >So if you want to test, build the tagged version of myfaces-maven on > > >your local machine. Please confirm ASAP since we would like to > > >release. > > > > > >Sean > > > > > >On 3/7/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote: > > >> Hi Sean! > > >> > Dennis mentioned that we are not using JDK 1.3 compile option on the > > >> > core branch. > > >> Its not only to set the target/source options, but also to > > >> a) set the bootclasspath for the compiler to the jdk1.3 libraries - see: > > >> http://jroller.com/page/scolebourne?entry=compiling_for_older_jdks and > > >> its comments > > >> or even better > > >> b) user a jdk1.3 compiler for the build. > > >> > > >> > > >> Ciao, > > >> Mario > > >> > > >> > > > > > > > > >
