[
https://issues.apache.org/jira/browse/BEANUTILS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088379#comment-18088379
]
Gary D. Gregory commented on BEANUTILS-577:
-------------------------------------------
I can create a 2.0.0 release candidate but I am not 100% that it won't lock us
into an API we'll want to change. I suppose we won't know for sure until 2.0.0
is in use. I'm not sure what 1.2.0 would buy you since it won't break BC. Am I
missing something? The conservative path would be another milestone just in
case. I'll review over the next couple of days.
> Update collections dependency to collections4
> ----------------------------------------------
>
> Key: BEANUTILS-577
> URL: https://issues.apache.org/jira/browse/BEANUTILS-577
> Project: Commons BeanUtils
> Issue Type: Improvement
> Reporter: Steve Lopez
> Priority: Minor
> Fix For: 2.0.0-M1
>
> Attachments: sonatype-2024-3350.png
>
>
> Latest version is dependent on old commons-collections (last updated in
> 2015).
> Request is to update commons-beanutils to use commons-collections4 as it is
> actively maintained. Completing this improvement will enable applicatios
> to reduce dependency footprint and reduce code bloat when the only library in
> an application needing the old commons-collections library is beanutils.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
