Since the old 2.0 branch is so... "sleepy" and I've not seen Simone here in
a long time, I'd rather keep the train moving as it is and if someone
really wants a breaking BC release, maybe that would be for a 3.0... or is
this simple a case of changing BU APIs from returning [collections]
concrete c
Hi,
> Am 30.12.2017 um 16:24 schrieb Gary Gregory :
>
> Who can speak to that code base?
I’ve worked on BeanUtils2 some years ago together with Simone Tripodi. I think
we should better work on this redesign instead oh pushing the old code base as
2.0 just to fix some dependencies. In fact I th
Who can speak to that code base?
Gary
On Dec 30, 2017 03:54, "Benedikt Ritter" wrote:
>
>
> > Am 29.12.2017 um 19:58 schrieb Gary Gregory :
> >
> > On Wed, Dec 27, 2017 at 11:55 AM, Gary Gregory
> > wrote:
> >
> >> The changes for:
> >>
> >> BEANUTILS-500 Upgrade commons-collections to 4
> >>
> Am 29.12.2017 um 19:58 schrieb Gary Gregory :
>
> On Wed, Dec 27, 2017 at 11:55 AM, Gary Gregory
> wrote:
>
>> The changes for:
>>
>> BEANUTILS-500 Upgrade commons-collections to 4
>>
>> break BC (see BEANUTILS-500).
>>
>> Therefore, I created BEANUTILS-503: Change packaging from
>> org.a
On Wed, Dec 27, 2017 at 11:55 AM, Gary Gregory
wrote:
> The changes for:
>
> BEANUTILS-500 Upgrade commons-collections to 4
>
> break BC (see BEANUTILS-500).
>
> Therefore, I created BEANUTILS-503: Change packaging from
> org.apache.commons.beanutils to org.apache.commons.beanutils2
>
> This chan
Agree, I can do this tonite.
Original message
From: Gary Gregory
Date: 12/27/17 1:55 PM (GMT-05:00)
To: Commons Developers List
Subject: [beanutils] Moving to beanutils2
The changes for:
BEANUTILS-500 Upgrade commons-collections to 4
break BC (see BEANUTILS-500).
The
