Last time I've used it, no warnings etc. were reported, and it just
silently breaks when I deploy my webapp to Tomcat running on JDK5.
If anyone knows about the warnings (and how to enable them), I'd love
to know ;-)
Regards,
Alex.
On Tue, Mar 18, 2008 at 2:06 PM, Jason Lee <jason_at_steeplesoft.com> wrote:
> On Mon, Mar 17, 2008 at 6:24 PM, Ken Paulsen <Ken.Paulsen_at_sun.com> wrote:
> >
> > Does the Java 6 compiler produce incompatible binaries when compiling
> > for Java 5? Or does it not warn when you use new Java 6 api's (like
> > String.isEmpty())? So far, JSFT does not use any Java 6 specific api's
> > and it should stay that way for a quite a while.
>
> I *think* that with the source level set to 1.5, the compiler will
> catch that, but I'll have to test to be sure. I'll need to install
> JDK 6 first though, which I might do anyway...
>
> --
>
> Jason Lee, SCJP
> Software Architect -- Objectstream, Inc.
> Mojarra and Mojarra Scales Dev Team
> https://mojarra.dev.java.net
> https://scales.dev.java.net
> http://blogs.steeplesoft.com
>