commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (BEANUTILS-290) Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project
Date Thu, 19 Jul 2007 22:52:06 GMT

     [ https://issues.apache.org/jira/browse/BEANUTILS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Niall Pemberton resolved BEANUTILS-290.
---------------------------------------

    Resolution: Fixed

I have merged the classes and unit tests back into core BeanUtils and removed the bean-collections
sub-module. Ant, Maven1 and Maven2 builds all work.

> Merge Bean-Collections back into core BeanUtils and remove Bean-Collections sub-project
> ---------------------------------------------------------------------------------------
>
>                 Key: BEANUTILS-290
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-290
>             Project: Commons BeanUtils
>          Issue Type: Task
>          Components: Bean-Collections
>    Affects Versions: 1.7.0
>            Reporter: Niall Pemberton
>            Assignee: Niall Pemberton
>            Priority: Minor
>             Fix For: 1.8.0
>
>
> 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).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message