Vadim Gritsenko wrote:
>
> > From: Sylvain Wallez [mailto:[EMAIL PROTECTED]]
> >
> > Carsten Ziegeler wrote:
> >
> > >Stefano Mazzocchi wrote:
> > >
> > >>Carsten Ziegeler wrote:
> > >>
> > >>>Christian Haul wrote:
> > >>>
> > >>>>there's a "-target <release>" switch to javac.
> > >>>
> > >>>Yes, and this is set to "1.2" (I hope) and afaiu it affects
> > >>>only the byte-code but not the "libraries/packages" used for
> > >>>compilation.
> > >>>
> > >>In Ant, there is a 'classic' compilation mode. Did you turn that on?
> > >>
> > >Yes, but with the same result.
> > >
> >
> > The "compiler" parameter in Ant choses the compiler, but not the set
> of
> > runtime classes used to compile sources.
> >
> > For this, we should use the "bootclasspath" parameter, which allows
> > cross-compilation for a different target JDK (not only classfile
> format
> > set by "target.vm", but also runtime classes). See more info on this
> at
> >
> http://java.sun.com/j2se/1.4/docs/tooldocs/windows/javac.html#crosscomp-
> > options
> >
> > Now the problem is how do we handle this in the build as I think we
> > cannot add a JDK 1.2 rt.jar in Cocoon's CVS ?
>
> It's a non-issue comparing to the real issue:
>
> 1. Compiling with JDK1.4 against JDK1.4's rt.jar gives incompatible with
> 1.3 code (IIRC, StringBuffer.append() issue)
> 2. Compiling with JDK1.4 against JDK1.3's rt.jar gives incompatible with
> 1.4 code (JDBC 3.0 is not in JDK1.3)
>
> Where is the exit from this loop?
Can't we make two different binary releases, one for 1.3 and 1.4 and
write a big "WARNING" note in a very visible place?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
