commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEANUTILS-379) Remove copied Collections classes
Date Tue, 11 Dec 2012 01:02:09 GMT

    [ https://issues.apache.org/jira/browse/BEANUTILS-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528541#comment-13528541
] 

Jason Dillon commented on BEANUTILS-379:
----------------------------------------

Is 1.8.4 ever going to get released?
                
> Remove copied Collections classes
> ---------------------------------
>
>                 Key: BEANUTILS-379
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-379
>             Project: Commons BeanUtils
>          Issue Type: Bug
>          Components: Bean / Property Utils
>    Affects Versions: 1.8.3
>            Reporter: Niall Pemberton
>            Assignee: Niall Pemberton
>             Fix For: 1.8.4
>
>
> In BeanUtils 1.7 four classes were copied from Commons Collections with the aim of removing
that dependency:
>     * ArrayStack
>     * Buffer
>     * BufferUnderflowException
>     * FastHashMap
> However there are other classes within BeanUtils that depend on Commons Collections (e.g.
BeanMap)  - so three flavours of jars were created:
>     * commons-beanutils.jar (all classes)
>     * commons-beanutils-core.jar (core beantils which doesn't require Commons Collections)
>     * commons-beanutils-bean-collections.jar (classes dependant on Commons Collections)
> This situation is a bit of a mess an is causing issues such as BEANUTILS-378
> I suggest the following action is taken in the next 1.x BeanUtils release:
>     * remove the copied Commons Collections classes
>     * add Commons Collections as a dependency
>     * Only produce the one commons-beanutils.jar
> Removing the dependency on the four collections classes is more difficult as some of
them are in BeanUtils API

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message