[
https://issues.apache.org/jira/browse/VALIDATOR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792530#comment-17792530
]
Elliotte Rusty Harold commented on VALIDATOR-390:
-------------------------------------------------
" This will be binary incompatible so will involve Maven coord and Java package
changes."
If getting rid of FastHashMap from the public API is the only breaking change,
I don't think Maven coord and Java package changes are required, or even a good
idea. IMHO it's enough to change the major version. Even with the FastHashMap
API changes, this can still be a drop-in replacement for almost all users. This
is a very minor part of the API. (I'm assuming there aren't other more
significant changes.) Indeed changing package names requires devs to rewrite
their code to upgrade. We should try to make the task easier for vast majority
of dependents who don't rely directly on FastHashMap.
Keeping the coords and packages the same will also help avoid cases where both
the old and the new versions appear in the classpath, leading to memory bloat
and possibly unexpected bugs.
> Upgrade to Commons Collections 4.x
> ----------------------------------
>
> Key: VALIDATOR-390
> URL: https://issues.apache.org/jira/browse/VALIDATOR-390
> Project: Commons Validator
> Issue Type: Improvement
> Reporter: Jake Brownell
> Priority: Minor
>
> Commons Validator 1.5 now uses Java 1.6. Commons Collections 4.0/4.1 has the
> same Java requirement.
> I noticed that CV seems to be the only one of many third party dependencies
> in my project that requires CC 3.2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
