Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 15046 invoked from network); 3 Oct 2007 23:15:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2007 23:15:42 -0000 Received: (qmail 6369 invoked by uid 500); 3 Oct 2007 23:15:31 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 6263 invoked by uid 500); 3 Oct 2007 23:15:31 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 6254 invoked by uid 99); 3 Oct 2007 23:15:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 16:15:31 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [68.142.198.208] (HELO smtp109.sbc.mail.mud.yahoo.com) (68.142.198.208) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 03 Oct 2007 23:15:32 +0000 Received: (qmail 60844 invoked from network); 3 Oct 2007 23:15:11 -0000 Received: from unknown (HELO ?9.72.133.166?) (ddebrunner@sbcglobal.net@32.97.110.142 with plain) by smtp109.sbc.mail.mud.yahoo.com with SMTP; 3 Oct 2007 23:15:10 -0000 X-YMail-OSG: x74gJAEVM1l281QL5bzbtJ3fUStC75uQZzuQ8LbFaS1e7AvW_0RthHHmoxUn_FqqydrqZ98DmQ-- Message-ID: <4704228C.4070905@apache.org> Date: Wed, 03 Oct 2007 16:15:24 -0700 From: Daniel John Debrunner 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Rick Hillegas writes: >> 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. +1 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. Examples are the for each loop, auto-boxing and some annotations. Something to try out anyway ... Dan.