[
https://issues.apache.org/jira/browse/CONFIGURATION-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262885#comment-13262885
]
Chris Seieroe commented on CONFIGURATION-482:
---------------------------------------------
Perhaps there's a bug with maven-bundle-plugin that doesn't automatically add
optional in this case. As a workaround, I added the following property to the
pom.xml file and forced "resolution:=optional" on those optional dependencies.
That seemed to do the trick.
<commons.osgi.import>
org.apache.commons.beanutils.*;resolution:=optional,
org.apache.commons.digester.*;resolution:=optional,
org.apache.commons.collections.*;resolution:=optional,
org.apache.commons.codec.*;resolution:=optional,
org.apache.commons.jxpath.*;resolution:=optional,
org.apache.xml.resolver.*;resolution:=optional,
javax.servlet.*;resolution:=optional,
org.apache.commons.jexl2.*;resolution:=optional,
org.apache.commons.vfs2.*;resolution:=optional,
*
</commons.osgi.import>
> Optional dependencies are not marked optional in the manifest's
> Import-Package section
> --------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-482
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-482
> Project: Commons Configuration
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.8
> Reporter: Chris Seieroe
> Priority: Minor
>
> The following page lists the runtime dependencies based on the components.
> This is reflected in the pom file since many are listed as optional (e.g.
> commons-jexl). However, if you want to use commons-configuration in an OSGi
> container, those become required because the corresponding packages are
> listed in the manifest's Import-Package section. They do not have the
> "resolution:=optional" qualifier on it so you get an error if you do not
> include something like commons-jexl yourself.
> http://commons.apache.org/configuration/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
