Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
From: "Mark Thomas" <markt@apache.org>
To: "'Commons Developers List'" <dev@commons.apache.org>
References: <ce1f2ea80901141323k5efe164agd750731e7372987c@mail.gmail.com>
 <496E98AE.7050604@btopenworld.com> <496EA885.5000006@gmail.com>
In-Reply-To: <496EA885.5000006@gmail.com>
Subject: RE: [DBCP] svn commit: r734473
Date: Thu, 15 Jan 2009 09:35:00 -0000
Message-ID: <002c01c976f4$89705cf0$9c5116d0$@org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acl2vomHSELhXTGXQ0GFxktD5qUsxwANcmDQ
Content-Language: en-gb

> From: Phil Steitz [mailto:phil.steitz@gmail.com]
> 
> Stephen Colebourne wrote:
> > Rahul Akolkar wrote:
> >>
> >> Note that the above breaks binary and source compatibility.
> Therefore,
> >> at the least, such changes deserve notable mentions in the release
> >> notes and often additional thought about the version number of the
> >> next release.
> >
> > We shouldn't create any more jar hell situations.
> I agree with Stephen on this.  This is a needless break.  I would
> prefer
> to limit changes to what is required to support compilation under JDK
> 1.6.   Otherwise, we need to target a 2.0 (and consider changing
> package
> name) and as there does not appear to be collective energy to push out
> a
> 1.2.3 bugfix release, I would really like to see 1.3 usable by current
> users as there are some nasty bugs that have been fixed in trunk.

+1

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org