commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Seieroe (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONFIGURATION-482) Optional dependencies are not marked optional in the manifest's Import-Package section
Date Mon, 05 Mar 2012 06:42:58 GMT

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

Chris Seieroe commented on CONFIGURATION-482:
---------------------------------------------

Looks like it already does as of version 2.3.4. If I'm reading the pom files correctly, commons-config
1.8 uses version 2.3.5. At least that's what I see in commons-parent version 23.

http://issues.apache.org/jira/browse/FELIX-954
http://issues.apache.org/jira/browse/FELIX-2809
                
> 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

        

Mime
View raw message