You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org> on 2011/10/04 05:59:34 UTC
[jira] [Commented] (CONFIGURATION-465) commons-configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119887#comment-13119887 ]
Ralph Goers commented on CONFIGURATION-465:
-------------------------------------------
Jexl is used in the ExprLookup class. If you don't use it in your DefaultConfigurationBuilder configuration then Jexl would not be required. I didn't realize that Jexl had this issue so I appreciate you letting us know about it. Jexl 2.x requires Java 1.5 so it would definitely have to be an optional dependency since Commons Configuration supports Java 1.4.
> 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