Uploaded image for project: 'Commons BeanUtils'
  1. Commons BeanUtils
  2. BEANUTILS-379

Remove copied Collections classes

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.8.3
    • 1.8.4
    • Bean / Property Utils
    • None

    Description

      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

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            niallp Niall Pemberton
            niallp Niall Pemberton
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment