commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alberto Mozzone (JIRA)" <>
Subject [jira] [Created] (BEANUTILS-398) CLONE - The three jars contain wrong classes
Date Wed, 10 Aug 2011 08:17:27 GMT
CLONE - The three jars contain wrong classes

                 Key: BEANUTILS-398
             Project: Commons BeanUtils
          Issue Type: Task
          Components: Bean-Collections
    Affects Versions: 1.7.0
            Reporter: Alberto Mozzone
            Assignee: Niall Pemberton
            Priority: Minor
             Fix For: 1.8.0

This issue has been discussed in the following thread:

For BeanUtils 1.7.0 the following classes which had a dependency on Commons Collections were
split into a separate "bean-collections" sub-module:

Three "flavours" of jars were released in 1.7.0

   commons-beanutils.jar - containing all BeanUtils classes, including above bean-collections
   commons-beanutils-bean-collections.jar - containing just the above  bean-collections classes
   commons-beanutils-core.jar - containing BeanUtils classes excluding above bean-collections

BeanUtils 1.7.0 was created using ant and (I presume) the maven poms for the above artifacts
were manually created - unfortunately with mistakes:

1) The pom for commons-beanutils.jar DOESN'T declare any Commons Collections dependency (which
it has for the bean-collections classes)
2) The pom for commons-beanutils-core.jar DOES declare a Commons Collections dependency (which
it doesn't actually have)

The proposal for BeanUtils 1.8.0 (see is to merge the bean-collections
classes back into core BeanUtils and get rid of the bean-collections sub-module - releasing
just a single jar for BeanUtils and marking the Commons Collections dependency as "optional"
in the maven pom (see

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message