commons-issues 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-386) Maven - missing dependency on Commons Collections
Date Fri, 14 Jan 2011 20:31:45 GMT

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

Niall Pemberton resolved BEANUTILS-386.
---------------------------------------

    Resolution: Invalid

BeanUtils 1.8.3 specifies commons-collections in its pom as a dependency which you can see
if you look here:

    * http://repo2.maven.org/maven2/commons-beanutils/commons-beanutils/1.8.3/commons-beanutils-1.8.3.pom

However it is marked as *optional* which means that you need to specify that dependency yourself
if you use those part of BeanUtils (such as BeanMap) that require it.

> Maven - missing dependency on Commons Collections
> -------------------------------------------------
>
>                 Key: BEANUTILS-386
>                 URL: https://issues.apache.org/jira/browse/BEANUTILS-386
>             Project: Commons BeanUtils
>          Issue Type: Improvement
>    Affects Versions: 1.8.3
>            Reporter: Enal Posi
>            Priority: Minor
>
> Our project is configured with a Maven dependency on commons-beanutils.
> BeanMap(Object) seems to have a dependency on org.apache.commons.collections.Transformer,
which is found in commons-collections. However, beanutils apparently does not imply this dependency,
resulting in class not found exceptions at runtime.
> Thanks

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


Mime
View raw message