@Matt Sicker
Like what I said before, there be no current active commons committers who
interested in developing bean-utils.
For example, commons-math have sebb, commons-lang & text & vfs have gary,
commons-compress have peterAL, but seems nobody is interested in
commons-beanutils
Currently
Matt,
I totally agree. I asked over and over for almost a year for a release.
I understand the contributors are busy. I was submitting PRs that were not
getting reviewed and merged. I have a client that had 2 concerns…the security
findings and the fact it still used commons collections 3
I don’t see why that couldn’t have been done here. There’s no need to fork
Commons projects when they’re fairly open to contributors.
—
Matt Sicker
> On Apr 20, 2022, at 16:19, Melloware Inc wrote:
>
> It was supposed to be temporary until Apache released 2.0. It’s been over 5
> years
It was supposed to be temporary until Apache released 2.0. It’s been over 5
years since last beanutils release so it’s a good thing I did in my opinion.
Melloware
@melloware on GitHub
> On Apr 20, 2022, at 3:31 PM, Gary Gregory wrote:
>
> You are crearting jar hell by reusing the Apache
You are crearting jar hell by reusing the Apache package names under
different Maven coordinates. Not a good idea IMO.
Gary
On Wed, Apr 20, 2022, 15:27 Melloware wrote:
> I did not the package names are the same I did this because I had
> multiple clients complaining about Commons Beantutils
I did not the package names are the same I did this because I had
multiple clients complaining about Commons Beantutils 1.9.4 security
vulnerabilities and needed a public version of the code so it could be
scanned. Whenever the REAL BeanUtils2 is ever released to Maven Central
my clients can
On Wed, 20 Apr 2022 at 18:54, Melloware wrote:
>
> And and I have forked it and deployed to Maven Central
>
>
>com.melloware
>commons-beanutils2
>2.0.0
>
>
Did you change the package names?
If not, there will be problems in the future if a project depends on
both via different
And and I have forked it and deployed to Maven Central
com.melloware
commons-beanutils2
2.0.0
On 4/20/2022 10:12 AM, Xeno Amess wrote:
Well I wonder should we give melloware (https://github.com/melloware) a
committer permission.
Since:
1. he has quite some experience here, not a
Well I wonder should we give melloware (https://github.com/melloware) a
committer permission.
Since:
1. he has quite some experience here, not a fresh hand.
2. he has ability to write/review good codes.(already several thousands
lines in common-beanutils).
3. he has enough time and interest to
There isn't one; we are all volunteers here ;-)
There is probably clean up to do, PRs, Jiras, releasing and synching with
Commons Collections 4.5 first (probably).
Gary
On Wed, Apr 20, 2022, 07:21 Martin Aldrin
wrote:
> Hi,
>
> I wonder what the time plan for release of beanutils2 is.
>
>
>
Hi,
I wonder what the time plan for release of beanutils2 is.
/Martin
11 matches
Mail list logo
