commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Bishop (JIRA)" <>
Subject [jira] [Commented] (BEANUTILS-418) OSGi Manifest for BeanUtils should optionally import commons-collections
Date Sat, 02 Mar 2013 05:21:13 GMT


Matt Bishop commented on BEANUTILS-418:

I worked through this issue on my machine and have create the following modification to commons-beanutils/pom.xml:


This needs to go in the <plugins> section of <build>. It overrides the default
bundle plugin in commons-parent pom.
> OSGi Manifest for BeanUtils should optionally import commons-collections
> ------------------------------------------------------------------------
>                 Key: BEANUTILS-418
>                 URL:
>             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
> Please change the import-package header to optionally import the commons collection classes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message