Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4705194B.3010802@apache.org>
Date: Thu, 04 Oct 2007 09:48:11 -0700
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [VOTE] Require Java 5 (or later) compiler to build Derby
References: <46FA62B4.3010102@sun.com> <x1o3lkalbsy0.fsf@sun.com>
 <4704228C.4070905@apache.org> <4704969A.2020002@sun.com>
 <4705053D.8030105@apache.org>
In-Reply-To: <4705053D.8030105@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Daniel John Debrunner wrote:
> Thomas Nielsen wrote:
>> Daniel John Debrunner wrote:
>>> Seems that it might be possible with this to start using some 1.5 
>>> language constructs in Derby's code: those that compile down to 
>>> standard byte code. This would be by using -source 1.5 -target 1.4 in 
>>> the build.xml files.
>>
>> Be *very* careful about what 1.5 language features you start using in 
>> your code. It's not as easy as specifying -source 1.5 -target 1.4 to 
>> get a 1.4 compatible class/jar.
>>
>> If you end up using the "wrong" language constructs in your code, you 
>> will become dependant on additional libraries like Retrowaver (or 
>> similar) that implements the missing features/classes for you.
> 
> To be clear I explicitly meant Java language constructs (ie. JLS), not 
> 1.5 new methods or classes. As Bryan said if you could share your 
> experience that would be helpful.

Never mind:

 > $JAVA_HOME/bin/javac -target 1.4 -source 1.5
javac: source release 1.5 requires target release 1.5

Dan.