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 will still build w/ Java 5 when publishing jars by hand to the
repositories just to be safe. :)
Thanks,
Ken
Alex Lam S.L. wrote:
> Be careful of String.isEmpty() - this and quite a few others bites me
> endless of times when using JavaSE 6 for JavaSE 5.0 codebase.
>
> Just my 2 cents,
> Alex.
>
>
> On Mon, Mar 17, 2008 at 10:02 PM, Jason Lee <jason_at_steeplesoft.com> wrote:
>
>> I just committed a change to the build system that will allow Ken can
>> happily use Java 6 to build. :)
>>
>> The build now defaults to a source level of 1.5 and compile target of
>> 1.5, so be sure to update you build files. Look at
>> build.properties.example (compile.target and source.version).
>>
>> --
>> 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
>>
>>