Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates
 209.85.216.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAE9L6G0O6xtE-D4T06Ddxv=uX48DZeNDM0VrUZ4RFpjnRwJUYw@mail.gmail.com>
References: 
 <1E9B117CDD4BB34481DB5DE25839A3361CFC4D32@ct1-mailbox-1-2.cybage.com>
	<CACzrW9BN0qfz5+QHzUiGuNEX-g+cVM=7hSwWDOQvLwhrLqTJ+A@mail.gmail.com>
	<CABLGb9xS2exzBtLftDNzTKFhJs4pory-HBSkGA+jF_tR1LtuHg@mail.gmail.com>
	<CAPVuaYv0WeSqcy3gJ702iRHE+eUVfvmTaGpSZWdoBgDFCQ9-4w@mail.gmail.com>
	<CAPVuaYv0OK9pULbPcSVrrrSyKo=2K6sDm19=bVj3FJETm-cAmQ@mail.gmail.com>
	<CAE9L6G3Aqvz0ixDgrVkq1r2AoASTLttEB=Tx=5f5s=1fYRuLVg@mail.gmail.com>
	<CAPVuaYu3jqBnWv6GNA8+C3NcpoHyuSsAoeCOE9wLZaQEiT4mCQ@mail.gmail.com>
	<CAE9L6G0O6xtE-D4T06Ddxv=uX48DZeNDM0VrUZ4RFpjnRwJUYw@mail.gmail.com>
Date: Thu, 28 Jul 2011 16:27:59 -0700
Message-ID: 
 <CAPVuaYtASCo_VZZZy3OOuDrOmqFoyiKgFrr9DKetaykmDiBrdQ@mail.gmail.com>
Subject: Re: [LANG] Commons Lang 3.0
From: Henri Yandell <flamefew@gmail.com>
To: gudnabrsam@gmail.com
Cc: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

That sounds like 'yes we should do that asap' to me :)

On Thu, Jul 28, 2011 at 4:24 PM, Matt Benson <gudnabrsam@gmail.com> wrote:
> Very nearly so, yes. =A0:)
>
> Matt
>
> On Thu, Jul 28, 2011 at 6:20 PM, Henri Yandell <flamefew@gmail.com> wrote=
:
>> Time to flip the 1.x trunk and 2.0 branch?
>>
>> On Thu, Jul 28, 2011 at 4:03 PM, Matt Benson <gudnabrsam@gmail.com> wrot=
e:
>>> I did the proxy 2.0 branch; not sure there's a reason to worry about
>>> the 1.x trunk.
>>>
>>> Matt
>>>
>>> On Thu, Jul 28, 2011 at 5:26 PM, Henri Yandell <flamefew@gmail.com> wro=
te:
>>>> Note that Chain isn't really depending on it. It depends on
>>>> myfaces-api and then excludes commons-lang.
>>>>
>>>> JCS, Flatfile and Pipeline are all upgraded in SVN. Configuration and
>>>> Proxy need updating.
>>>>
>>>> Hen
>>>>
>>>> On Wed, Jul 27, 2011 at 8:32 AM, Henri Yandell <flamefew@gmail.com> wr=
ote:
>>>>> For the record, and so we can consider what needs a release, the
>>>>> following components depend on Lang:
>>>>>
>>>>> * Chain
>>>>> * Configuration
>>>>> * JCS
>>>>> * Proxy
>>>>>
>>>>> and in the Sandbox:
>>>>>
>>>>> * Flatfile
>>>>> * Pipeline
>>>>>
>>>>> Hen
>>>>>
>>>>> On Wed, Jul 27, 2011 at 6:13 AM, Paul Benedict <pbenedict@apache.org>=
 wrote:
>>>>>> Yes. The reason the package name was changed was so that 1.x-2.x and
>>>>>> 3.0 can coexist together in an application. Since Commons
>>>>>> Configuration relies on a previous version, as Stephen said, you wil=
l
>>>>>> need both dependencies.
>>>>>>
>>>>>> On Wed, Jul 27, 2011 at 7:53 AM, Stephen Colebourne
>>>>>> <scolebourne@joda.org> wrote:
>>>>>>> You will need both versions of commons-lang, the new and the old.
>>>>>>> Stephen
>>>>>>>
>>>>>>> On 27 July 2011 11:17, Rohan Kadam <rohanka@cybage.com> wrote:
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> We have upgraded our common lang jar to 3.0 version. We have repla=
ced package name "lang" to "lang3". But since it has already been mentioned=
 on apache website that Common Lang 3.0 is not backward compatible, we are =
facing some compilation issues.
>>>>>>>>
>>>>>>>> After replacing Apache Commons Lang 2.1 with Apache Commons Lang 3=
.0 we get some compilation errors since the class org.apache.commons.lang.e=
xception.NestableException is being referred internally in the class files =
of =A0org.apache.commons.configuration.ConfigurationException.
>>>>>>>>
>>>>>>>> To summarize the common lang jar to 3.0 version is not compatible =
with common configuration jar latest version.
>>>>>>>>
>>>>>>>> Please suggest.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> "Legal Disclaimer: This electronic message and all contents contai=
n information from Cybage Software Private Limited which may be privileged,=
 confidential, or otherwise protected from disclosure. The information is i=
ntended to be for the addressee(s) only. If you are not an addressee, any d=
isclosure, copy, distribution, or use of the contents of this message is st=
rictly prohibited. If you have received this electronic message in error pl=
ease notify the sender by reply e-mail to and destroy the original message =
and all copies. Cybage has taken every reasonable precaution to minimize th=
e risk of malicious content in the mail, but is not liable for any damage y=
ou may sustain as a result of any malicious content in this e-mail. You sho=
uld carry out your own malicious content checks before opening the e-mail o=
r attachment."
>>>>>>>> www.cybage.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------=
---
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> -------------------------------------------------------------------=
--
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------=
-
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>

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