project_key: JBPAPP6 org.apache.commons.collections.ArrayStack org.apache.commons.collections.Buffer org.apache.commons.collections.BufferUnderflowException org.apache.commons.collections.FastHashMap org.apache.commons.collections.FastHashMap$1 org.apache.commons.collections.FastHashMap$CollectionView org.apache.commons.collections.FastHashMap$CollectionView$CollectionViewIterator org.apache.commons.collections.FastHashMap$EntrySet org.apache.commons.collections.FastHashMap$KeySet org.apache.commons.collections.FastHashMap$Values Refer to this TattleTale report: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/as7-tattletale/javadoc/classlocation/index.html
Link: Added: This issue Cloned from AS7-3390
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW
Our product build of commons-beanutils also contains the repackaged classes from commons-collections. Do we need to separate these classes?
Most of the poms already have a commons-collections dependency, but it's marked optional. Commons-Collections ------------------- BeanUtils now ships with a small number of commons collections classes. This is a temporary measure intended to allow BeanUtils core to be used with either commons-collections 2 or commons-collections-3 without a dependency on either. It is intended that soon BeanUtils core will have no dependency on any commons collection packaged classes.
Classes removed from build apache-commons-beanutils-1.8.3-4.7_redhat_1.ep6.el6.
If the product version of the jar is different from the upstream jar, it needs to be documented in the wiki: https://docspace.corp.redhat.com/docs/DOC-87781
Documented in Version 5.
Verified on EAP 6.0.0 ER1 http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/eap-60-tattletale/javadoc/multiplejars/index.html
Docs QE Status: Removed: NEW