[
https://issues.apache.org/jira/browse/COLLECTIONS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Neidhart resolved COLLECTIONS-483.
-----------------------------------------
Resolution: Won't Fix
Hi Brahim,
I really appreciate your work, and if we would do a greenfield project, this
would be the right way to go.
Doing such a fundamental change in a matured library like collections is not
easy and would certainly be very controversial, thus I close this for now as
Won't fix. If you are still determined to push collections in this direction
for a potential 5.0 release, I would suggest to discuss the change on the
mailinglist to get feedback from the community and if positive we can re-open
the issue.
Thanks,
Thomas
> Cyclic dependencies among several packages.
> -------------------------------------------
>
> Key: COLLECTIONS-483
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-483
> Project: Commons Collections
> Issue Type: Improvement
> Affects Versions: 4.0-alpha1, 4.0
> Reporter: Brahim Djoudi
> Priority: Minor
> Attachments: c4-refactored.png, c4-refactoring.pdf, c4-src.zip, c4.png
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Many packages have mutual dependency, directly or undirectly.
> These dependencies may be avoided just by moving some classes and interfaces
> within different packages.
> This refactoring breaks API compatibility but enhances the useability and the
> maintainability (hopefully) of the library. In addition, few issues in
> dynamic environments (like OSGi) less occur.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
