You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2013/11/10 21:48:17 UTC
[jira] [Commented] (BEANUTILS-418) OSGi Manifest for BeanUtils
should optionally import commons-collections
[ https://issues.apache.org/jira/browse/BEANUTILS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818544#comment-13818544 ]
Oliver Heger commented on BEANUTILS-418:
----------------------------------------
I agree with Nial. After the removal of the classes originally copied from Collections, the dependency is no longer optional. For instance, {{PropertyUtils}} - a central class of BeanUtils - uses {{FastHashMap}} from Collections.
So I think this issue should be closed as won't fix.
> OSGi Manifest for BeanUtils should optionally import commons-collections
> ------------------------------------------------------------------------
>
> Key: BEANUTILS-418
> URL: https://issues.apache.org/jira/browse/BEANUTILS-418
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: Bean / Property Utils
> Affects Versions: 1.8.3
> Environment: Any OSGi environment
> Reporter: Matt Bishop
> Priority: Minor
>
> The docs for BeanUtils clearly state that commons-collections is an optional dependency, but when using Beanutils in OSGi this dependency is actually required. This is due to the fact that the manifest requires the commons-collection packages rather than optionally requires them.
> Please change the import-package header to optionally import the commons collection classes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)