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 2012/05/22 22:23:42 UTC
[jira] [Resolved] (CONFIGURATION-482) Optional dependencies are not
marked optional in the manifest's Import-Package section
[ https://issues.apache.org/jira/browse/CONFIGURATION-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-482.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.9
Fixed in subversion in revision 1341612. The property suggested by Chris was added to the pom. Many thanks!
> 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
> Fix For: 1.9
>
>
> 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