-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove use of commons collections 3 coming via beanutils #260
Comments
I think it is too early to consider this. We are not using snapshots. |
Thanks for quick response. Commons Digester also seems to be EOL as well. Also does not looks like it is being actively maintained. Last release 3.2 was in 2011. Found that Apache Commons Digester used is v.2.1, a version that has been released in 2010. |
I think Digester is "Feature Complete", not "End of Life". It does what we need and we don't need anything more from it. |
Hello, any updates to it? commons-collections 3 is mentioned in vulnerability alerts (Cx78f40514-81ff) |
PR submitted |
commons collections 3 is EOL and there is no new version available since Nov, 2015 after 3.2.2. So it would make sense to remove its use within jasperreports going forward. Our customers have shown concern about its continued use and hence the request.
Currently there is dependency of commons-beanutils 1.9.4. There is major version of beanutils released commons-beanutils2 which no longer needs commons collections 3 and uses commons collections 4 in its place.
Will it be possible to upgrade to use commons-beanutils2?
Edit: Would like point out that it turns out that official beanutils is still not out yet. It is still in SNAPSHOT. But it is released by Melloware on Maven. More information: https://issues.apache.org/jira/browse/BEANUTILS-532
The text was updated successfully, but these errors were encountered: