commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEANUTILS-418) OSGi Manifest for BeanUtils should optionally import commons-collections
Date Mon, 11 Nov 2013 21:03:17 GMT

    [ https://issues.apache.org/jira/browse/BEANUTILS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819385#comment-13819385
] 

Oliver Heger commented on BEANUTILS-418:
----------------------------------------

Thomas, thanks for this hint. We should definitively replace FastHashMap sooner or later.

Unfortunately, the class appears in the public API of BeanUtils, so this can only be done
in a major release. There are also a couple of other classes from Commons Collections used
by BeanUtils. I guess, for the upcoming release the dependency cannot be dropped.

> 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)

Mime
View raw message