[
https://issues.apache.org/jira/browse/BEANUTILS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591303#comment-13591303
]
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:
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<configuration>
<instructions>
<Import-Package>
org.apache.commons.collections;resolution:=optional,
org.apache.commons.collections.comparators;resolution:=optional,
org.apache.commons.collections.keyvalue;resolution:=optional,
org.apache.commons.collections.list;resolution:=optional,
org.apache.commons.collections.set;resolution:=optional,
*
</Import-Package>
</instructions>
</configuration>
</plugin>
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: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
