Hi Simon,
The best thing to do IMO is to go through Jira and Github and address any
issues, especially ones that require breaking binary compatibility. A major
release like this one is the only opportunity we have to make breaking
changes. Let's make sure we take advantage of it.
One issue is whe
Hi Gary,
is there anything that can be done to help addressing the issues that prevent
beanutils2 from being released?
It's blocking the upgrade of a few dozen other open-source libraries, which in
turn causes dependencies on commons-collections v3 all over the place.
Please let me know if I ca
On Fri, Oct 5, 2018 at 1:01 PM Simon Ochsenreither
wrote:
> Hi Gary,
>
> I added the Automatic Module Name and sent a PR request
> (https://github.com/apache/commons-beanutils/pull/4) a while ago ... is
> there
> anything I can do to help moving this forward?
>
In svn trunk now. Tracking with
ht
Hi Gary,
I added the Automatic Module Name and sent a PR request
(https://github.com/apache/commons-beanutils/pull/4) a while ago ... is there
anything I can do to help moving this forward?
Thanks,
Simon
Hi Simon.
You're welcome :-)
I do not have a schedule. I would guess within a month,
Please provide a PR for your change, it's just so much easier for me to
deal with.
Also please review what we have in Git master now.
I encourage you to test your software with a SNAPSHOT version to make sure
Hi Gary,
first of all thanks for doing all the work and updating these libraries.
Two short questions:
- Do you have an estimated time until beanutils2 ships (days, weeks, months)?
- Would it be possible to add a Automatic-Module-Name entry to the MANIFEST.MF
file for better Java 9 support?
I
Long term I think we can get rid of the dependency on Commons Collection by
updating to Java 8 and lambas. So an incremental plan could be:
- Now: BeanUtils 1.x (commons-beanutils) depends on Commons Collection 3
(commons-collections).
- Next: BeanUtils 2.x (commons-beanutils2) depends on Commons
Hi All:
Once I am done with releasing Commons Collections 4.2, I plan on releasing
Commons BeanUtils 2.
This will be a major version change due to the update from Commons
Collections 3 to 4.
If you want to change BeanUtils so that Commons Collections classes are NOT
surfaced in the BeanUtils pub
