[BEANUTILS-290] Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.8.0
• Component/s: Bean-Collections
• Assignee: Niall Pemberton
• Reporter: Niall Pemberton
• Created: 19/Jul/07 17:13
• Updated: 10/Aug/11 08:15
• Resolved: 19/Jul/07 22:51

Description

This issue has been discussed in the following thread: http://tinyurl.com/2xdpku

For BeanUtils 1.7.0 the following classes which had a dependency on Commons Collections were split into a separate "bean-collections" sub-module:
BeanComparator.java
BeanMap.java
BeanPredicate.java
BeanPropertyValueChangeClosure.java
BeanPropertyValueEqualsPredicate.java
BeanToPropertyValueTransformer.java

Three "flavours" of jars were released in 1.7.0

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

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 http://tinyurl.com/2xdpku) 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 http://tinyurl.com/2nm2bu).

Issue Links

• is cloned by: BEANUTILS-398 CLONE - The three jars contain wrong classes