commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Mayfield (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONFIGURATION-465) commons-configuration
Date Tue, 04 Oct 2011 09:20:34 GMT

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

Rich Mayfield commented on CONFIGURATION-465:
---------------------------------------------

Thanks for the response.  By default, packages listed in the MANIFEST.MF Import-Package header
is considered required.  You can, however, make package imports "optional" in cases like you
have described.

If it is the case that the class that references Jexl (ExprLookup) is never loaded via the
bundle classloader for commons-configuration, then making that package dependency optional
should do the trick.
                
> commons-configuration 
> ----------------------
>
>                 Key: CONFIGURATION-465
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-465
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.7
>            Reporter: Rich Mayfield
>
> I updated to use commons-configuration 1.7 (from 1.6) and am running into the following
resolution error under Eclipse Equinox OSGi framework.
>         An Import-Package could not be resolved. Caused by missing constraint in bundle
<org.apache.commons.configuration_1.7.0>
>              constraint: <Import-Package: org.apache.commons.jexl; version="0.0.0">
> According to the Import-Package header in 1.7's MANIFEST.MF, commons-configuration now
has a required dependency on org.apache.commons.jexl.  Problem is, there is no OSGi enabled
version of Apache Commons jexl that exports this package.
> In jexl 2.0 the packages were renamed and org.apache.commons.jexl2 is exported.  The
1.x codeline, although using org.apache.commons.jexl, does not have the appropriate MANIFEST.MF
headers to be used as an OSGi bundle.
> As such, you cannot consume commons-configuration 1.7 in an OSGi environment.

--
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