Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Wed, 26 Sep 2007 14:48:44 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: [VOTE] Require Java 5 (or later) compiler to build Derby
In-reply-to: <46FAA2B9.8020705@sbcglobal.net>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <46FAD3BC.9020104@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <46FA62B4.3010102@sun.com> <46FAA2B9.8020705@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)

Mike Matrigali wrote:
> If I only have jdk1.5 environment will the build succeed, and if so will
> it identify if I have somehow used a jdk1.5 specific library function in
> a "non-optional" part of the code?
Hi Mike,

You will still need jdk 1.4 and you will still need to set j14lib in 
your ant.properties. That doesn't change. The Java 5 compiler will 
object if mandatory code uses a Java 5 feature.
>
> How is optional vs. non-optional code specified?  Is this an ant xml 
> file property in the directory for the code?
Today, by default, all code is mandatory. You have to go out of your way 
to make code optional. I think that's a good model and I think we should 
stick with this model as we go forward. Today there are special build 
targets for the optional JSR169 and JDBC4 code. I think this is a good 
model to follow when we start introducing optional code which only runs 
on Java 5.

Regards,
-Rick
>
> /mikem
>
> Rick Hillegas wrote:
>> Please vote on whether we should require that developers use a Java 5 
>> (or later) compiler in order to build Derby. This means that the 
>> shell window running the build should have its JAVA_HOME pointed at a 
>> Java 5 or later jdk and the corresponding javac should be what's 
>> visible on PATH. The practical implication of this change is that the 
>> Derby build will fail when run from a jdk1.4 environment.
>>
>> Please note that, even after this vote, we still expect the following 
>> to hold:
>>
>> 1) All mandatory Derby code must still be at jdk1.4 (or earlier) 
>> level. The build will still compile mandatory code into classes that 
>> run on jdk1.4.
>>
>> 2) Derby 10.4 will continue to run on the same platforms that 10.3 
>> does--including the CDC small platforms.
>>
>> This change will make the following possible:
>>
>> A) Optional product code can be written which takes advantage of Java 
>> 5 features. This code will only run if Derby detects that it is 
>> running on a vm at level Java 5 or later.
>>
>> B) Test code can be written to make sure that Derby correctly 
>> interacts with user code which is at Java 5 level or later.
>>
>> This is a lazy consensus vote. The polls close at 5:00 pm on 
>> Wednesday October 3.
>>
>> Regards,
>> -Rick
>>
>