I suppose doing both wouldn’t be unreasonable. It’ll take me a few weeks as I’m
in the ramp up phase at a new gig. But I’ll start heading that direction.
-Rob
> On Jun 5, 2019, at 8:39 AM, Melloware wrote:
>
> Do you think we could also get a BeanUtils2 release while we are at it? It
> suppo
Do you think we could also get a BeanUtils2 release while we are at it?
It supports Java 8 and has many fixes in the last 3 years.
On 6/5/2019 8:37 AM, Rob Tompkins wrote:
I can try to backport the fix to the 1.X branch.
-Rob
On 6/5/2019 8:09 AM, Melloware wrote:
Rob,
I 100% agree since C
I can try to backport the fix to the 1.X branch.
-Rob
On 6/5/2019 8:09 AM, Melloware wrote:
Rob,
I 100% agree since CVE-2014-0114 has been fixed in BeanUtils I think
we need a release.
However the 1.X branch seems dormant it seems for the last 3 years
everything has been working on is Bean
Note that BeanUtils 2 is a major update with a package name change, meaning
it is not a drop in replacement.
The one main remaining issue to discuss IIRC is whether the BU API should
make public Commons Collections interface and classes, as opposed to more
generic JRE Collections.
Gary
On Wed, J
Rob,
I 100% agree since CVE-2014-0114 has been fixed in BeanUtils I think we
need a release.
However the 1.X branch seems dormant it seems for the last 3 years
everything has been working on is BeanUtils2 which is where all the
fixes have been made?
Mello
I think we’re heading towards the need for a release of beanutils 1.10. Does
anyone agree or disagree?
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
