Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 90037 invoked from network); 19 Jun 2009 18:34:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jun 2009 18:34:21 -0000 Received: (qmail 11056 invoked by uid 500); 19 Jun 2009 18:34:32 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 10971 invoked by uid 500); 19 Jun 2009 18:34:31 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 10963 invoked by uid 99); 19 Jun 2009 18:34:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 18:34:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jankeesvanandel@gmail.com designates 209.85.220.220 as permitted sender) Received: from [209.85.220.220] (HELO mail-fx0-f220.google.com) (209.85.220.220) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 18:34:22 +0000 Received: by fxm20 with SMTP id 20so1951585fxm.12 for ; Fri, 19 Jun 2009 11:34:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=aJY7UGTTsSr4pLz4SZ6Vh1Yeabeqof5tmrC4wxuuYuM=; b=hhFUSlMcoZfbdxPqpwO7WSkshwI+8bejpKIhEOf2F6D6mHbEywkHLvVkXvATkdq0cP srNwdV7QJhyaLlth19aM3kNYRNHFwdCOsqsE/rzK9UA3pWhOuES3NQR7UkTMpFg9qM6f XKXDdTDByzDMKT6cTLDmMgAmdx1P4OpPgxz70= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=AK5R2JMJd3+D0aFnY3ul0Sy5nv+jzAs7oFw2Z1cXuTz+dqs/3tf1C2i82fJJfjEOkw xWPp1QgSYCCN03YRfnhG9pZtIAZ3byvK4ckYmnUdIx5DGCodc/xsYl/R38TH7lEUaIH6 SPmsfQWooqBO8nHnzN3SjPw1Sb9tDyDtN7gsM= MIME-Version: 1.0 Received: by 10.103.11.7 with SMTP id o7mr2054001mui.95.1245436442292; Fri, 19 Jun 2009 11:34:02 -0700 (PDT) In-Reply-To: References: <1245409406.20507.52.camel@markoc.uvoz.aura.cz> <1a681ff20906190347v37d7b58ap4f74ca70c78c16a2@mail.gmail.com> Date: Fri, 19 Jun 2009 20:34:02 +0200 Message-ID: <237ac0b0906191134h43325c9fh8bd03b64ffcf0822@mail.gmail.com> Subject: Re: [Trinidad] JDK5 EOL, upgrade to JDK6? From: Jan-Kees van Andel To: MyFaces Development Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Do you mean the @Override annotation on interface implementing methods? Yeah, that's annoying. But IMHO no reason to force users to move to JDK 6. The companies I see, are currently using 5 (some even use 1.4). What feature of JDK 6 do you want to use? Besides the (Concurrent) Collections API I don't know any features that are of much use for Trinidad. I think it's very important for any software library to keep its users happy. Forcing users into a new JDK if they want to upgrade (maybe because they are interested in a bug fix) won't make them very happy. /JK 2009/6/19 Andrew Robinson : > We currently force JDK 5 in the maven build because we were having > problems with developers checking in JDK6 specific code and not > realizing it. > > -Andrew >