[
https://issues.apache.org/jira/browse/CONFIGURATION-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078789#comment-18078789
]
Gary D. Gregory commented on CONFIGURATION-776:
-----------------------------------------------
Hi All,
The issue COLLECTIONS-701 cannot happen in _Commons BeanUtils 1.x_ or _Commons
Configuration 2.x_ because these do not use {_}Commons Collection 3.x{_}'s
{{{}SetUniqueList{}}}.
Since there are other higher priority issues in Commons overall (bug fixes and
reviewing security reports), releasing a major version of Configuration just to
bump a dependency is not reasonable at this time. A major version of
Configuration to pick up a new BeanUtils 2 would break binary compatibility and
therefore would require a Configuration package name change from
configuration2" to "configuration3". At that time, we'll need to remove
deprecated elements, and review any other changes we can take advantage of
during this unique opportunity.
We should consider if it is desired in a future "configuration3" to create a
facade to BU to avoid such future issues.
HTH
> Update Commons BeanUtils from 1.9. to 2.X
> -----------------------------------------
>
> Key: CONFIGURATION-776
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-776
> Project: Commons Configuration
> Issue Type: Task
> Affects Versions: 2.6
> Reporter: Melloware
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Update Apache Commons BeanUtils from 1.9. to 2.X
> BeanUtils 2.X removes its dependency on Commons Collections but does change
> package name to the beanutils2 package.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
