Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 79259 invoked from network); 10 Mar 2006 00:17:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Mar 2006 00:17:03 -0000 Received: (qmail 52485 invoked by uid 500); 10 Mar 2006 00:17:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 52249 invoked by uid 500); 10 Mar 2006 00:17:01 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 52237 invoked by uid 99); 10 Mar 2006 00:17:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2006 16:17:00 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.182.199 as permitted sender) Received: from [64.233.182.199] (HELO nproxy.gmail.com) (64.233.182.199) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2006 16:17:00 -0800 Received: by nproxy.gmail.com with SMTP id n15so465405nfc for ; Thu, 09 Mar 2006 16:16:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=mOkSyq7bYalDALyBhtfdrTiYjWyDntdd34dtQj/IM6Wucj8aQw5i7OTdFGufm6Nk2itiGYwKg/ce3AvIGQmcXQTbtacUAAWgmGUnake7K3e3yyo3WrJkIJF6F+vALCFX4XY4T1ihtTFFGOvSs/oaD1TT/8YakW8yC7Jozto6c4M= Received: by 10.48.226.12 with SMTP id y12mr1161849nfg; Thu, 09 Mar 2006 16:16:38 -0800 (PST) Received: by 10.49.64.13 with HTTP; Thu, 9 Mar 2006 16:16:38 -0800 (PST) Message-ID: <768dcb2e0603091616r4f2942c8q72a70aba335e654@mail.gmail.com> Date: Fri, 10 Mar 2006 09:16:38 +0900 From: "Trustin Lee" To: "Apache Directory Developers List" Subject: Re: Shall we go JDK 1.5 in 1.1 branch In-Reply-To: <6.0.0.22.0.20060309191916.03e180b0@mail.qos.ch> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10889_163080.1141949798948" References: <440DA670.5050801@apache.org> <768dcb2e0603071528u2c9c895csad3f410e7b0d2391@mail.gmail.com> <6.0.0.22.0.20060309191916.03e180b0@mail.qos.ch> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_10889_163080.1141949798948 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 3/10/06, Ceki G=FClc=FC wrote: > > > I tried to summarize some of the arguments given here in my blog (see > below). In a nutshell, aiming for JDK 1.4 compatibility using JDK 1.5 > language features is likely to be messy, especially if you accept patches > from "outside" developers. On the other hand, who would blame you to want > to switch to JDK 1.5 when JDK 1.6 is in the offing? I'd like to say maintaining the backward compatibiliy can become messy just because of the lack of the feature in retrotranslator, not because of the techinique itself. If retrotranslator builds an API dictionary which contains the API difference between JDK 1.4 and 1.5, then we can return an error while translation very easily without much cost. Actually, I want to contribute this feature to the retrotranslator team. Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6 ------=_Part_10889_163080.1141949798948 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 3/10/06, Ceki G=FClc=FC <listid@qos.ch> wrote:

I tried to summarize some of the arguments given here in my blog (seebelow). In a nutshell, aiming for JDK 1.4 compatibility using JDK 1.5
= language features is likely to be messy, especially if you accept patches
from "outside" developers. On the other hand, who would blame= you to want
to switch to JDK 1.5 when JDK 1.6 is in the offing?

I'd like to say maintaining the backward compatibiliy can bec= ome messy just because of the lack of the feature in retrotranslator, not b= ecause of the techinique itself.  If retrotranslator builds an API dic= tionary which contains the API difference between JDK=20 1.4 and 1.5, then we can return an error while translation very easily with= out much cost.  Actually, I want to contribute this feature to the ret= rotranslator team.

Trustin
--
what we call human natu= re is actually human habit
--
http://gleamynode.net/
= --
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 5= 44D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC = 0255 ECA6 ------=_Part_10889_163080.1141949798948--