commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <>
Subject [jira] Created: (BEANUTILS-379) Remove copied Collections classes
Date Thu, 02 Sep 2010 16:26:53 GMT
Remove copied Collections classes

                 Key: BEANUTILS-379
             Project: Commons BeanUtils
          Issue Type: Bug
          Components: Bean / Property Utils
    Affects Versions: 1.8.3
            Reporter: Niall Pemberton

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.
You can reply to this email to add a comment to the issue online.

View raw message