Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 47334 invoked from network); 18 Aug 2009 11:07:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Aug 2009 11:07:42 -0000 Received: (qmail 80513 invoked by uid 500); 18 Aug 2009 11:08:00 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 80471 invoked by uid 500); 18 Aug 2009 11:08:00 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 80463 invoked by uid 99); 18 Aug 2009 11:08:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2009 11:08:00 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of brandon.goodin@gmail.com designates 209.85.218.227 as permitted sender) Received: from [209.85.218.227] (HELO mail-bw0-f227.google.com) (209.85.218.227) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2009 11:07:52 +0000 Received: by bwz27 with SMTP id 27so2715791bwz.34 for ; Tue, 18 Aug 2009 04:07:30 -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; bh=KZrIprn5VlbpgHnXFtqHUysRCoFF50ga7+fP9b60u9Q=; b=l6K3cSD2wcBKE0Ty3EOlcCuRO5pXHkvn0RgLtNmdrMFWy9Z8T6tBk0hEcSMUzVAKQc +GOKgGMV3tSd9U/T6ep4cQkyahGk8W1aLTzxRr0O1ULb2Ia3VI2RaywnnSHIcKPQIelV 2sigtJ961B952ubWxeTR2cy1fUX5j9VHOY2pc= 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; b=nON+WEvJgxI6iHFVQ04m/INj7sfb0j8HrWSw6AlJzmT0j9SNCOuURzxGTtx8ABKaUQ I6libuOaUIHlSijeyCRefCQ/bieM2oe7ysqBUkSJS3YHYS3lhMRUPQ1iNRJa9lUtb74r 4ipA9V5eTbawfmMaT7RcVclspA2MV3NwkHh9o= MIME-Version: 1.0 Received: by 10.223.144.149 with SMTP id z21mr1071134fau.8.1250593650578; Tue, 18 Aug 2009 04:07:30 -0700 (PDT) In-Reply-To: <1482511441.22595751250574990438.JavaMail.root@amundsen.cs.athabascau.ca> References: <1482511441.22595751250574990438.JavaMail.root@amundsen.cs.athabascau.ca> Date: Tue, 18 Aug 2009 06:07:30 -0500 Message-ID: <2fe5ef5b0908180407t43a4d639pf00e8eec579e3bc5@mail.gmail.com> Subject: Re: micro version JVM support From: Brandon Goodin To: user-java@ibatis.apache.org, "Trenton D. Adams" Content-Type: multipart/alternative; boundary=0023545306684d157604716886c9 X-Virus-Checked: Checked by ClamAV on apache.org --0023545306684d157604716886c9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit It depends on whether another significant version of the JVM ever comes out. In the current state of Java. It is unlikely that 6 or 7 (or 8) are going to have any significant features that will compel us to upgrade. But, who knows... once 6 hits its end of life... we may drop support in a micro version. Next time we'll try to remember to do it in a minor version. A couple things i will suggest to help you avoid being too surprised. First, have a good suite of unit tests. Secondly, if your software is dependent on 1.4 make sure your IDE is using the 1.4 compiler during development. You will find out pretty quickly that a jar is not 1.4 compatible and avoid any major error during an upgrade. Thanks, Brandon On Tue, Aug 18, 2009 at 12:56 AM, Trenton D. Adams wrote: > Hi Guys, > > I was very surprised to find out that 2.3.0 was the last version that > supported Java 1.4.2, and yet the latest version is only 4 micro versions > above 2.3.0, sitting at 2.3.4. Why would iBatis change something so major, > in a micro version? I would have expected that iBatis would have at the > very least, moved to 2.4, before declaring Java 1.4.2 unsupported. Even if > that's the ONLY change, it is worth a minor version change. > > Is this going to happen again, when the next JVM comes out? > > Thanks. > > Trenton D. Adams > Systems Analyst/Web Software Engineer > Navy Penguins at your service! > Athabasca University > (780) 675-6195 > :wq! > > __ > This communication is intended for the use of the recipient to whom it > is addressed, and may contain confidential, personal, and or privileged > information. Please contact us immediately if you are not the intended > recipient of this communication, and do not copy, distribute, or take > action relying on it. Any communications received in error, or > subsequent reply, should be deleted or destroyed. > --- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org > For additional commands, e-mail: user-java-help@ibatis.apache.org > > --0023545306684d157604716886c9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It depends on whether another significant version of the JVM ever comes out= . In the current state of Java. It is unlikely that 6 or 7 (or 8) are going= to have any significant features that will compel us to upgrade. But, who = knows... once 6 hits its end of life... we may drop support in a micro vers= ion. Next time we'll try to remember to do it in a minor version.=A0
A couple things i will suggest to help you avoid being too s= urprised. First, have a good suite of unit tests. Secondly, if your softwar= e is dependent on 1.4 make sure your IDE is using the 1.4 compiler during d= evelopment. You will find out pretty quickly that a jar is not 1.4 compatib= le and avoid any major error during an upgrade.

Thanks,
Brandon

On Tue, Aug 18, 2009 at 12:56 AM, Trenton D. Adams <trenta@athabascau.ca> wrote:
Hi Guys,

I was very surprised to find out that 2.3.0 was the last version that suppo= rted Java 1.4.2, and yet the latest version is only 4 micro versions above = 2.3.0, sitting at 2.3.4. =A0Why would iBatis change something so major, in = a micro version? =A0I would have expected that iBatis would have at the ver= y least, moved to 2.4, before declaring Java 1.4.2 unsupported. =A0Even if = that's the ONLY change, it is worth a minor version change.

Is this going to happen again, when the next JVM comes out?

Thanks.

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__
=A0 =A0This communication is intended for the use of the recipient to whom= it
=A0 =A0is addressed, and may contain confidential, personal, and or privil= eged
=A0 =A0information. Please contact us immediately if you are not the inten= ded
=A0 =A0recipient of this communication, and do not copy, distribute, or ta= ke
=A0 =A0action relying on it. Any communications received in error, or
=A0 =A0subsequent reply, should be deleted or destroyed.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org


--0023545306684d157604716886c9--