commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (Commented) (JIRA)" <>
Subject [jira] [Commented] (CONFIGURATION-465) OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release
Date Sun, 22 Jan 2012 15:46:40 GMT


Oliver Heger commented on CONFIGURATION-465:

Thanks for reviewing.

I was also wondering whether the Jexl classes are thread-safe and finally found the information
(in the package documentation for o.a.c.jexl2) that JexlEngine actually is. However, I doubt
that the same is true for MapContext because it is just a wrapper around a HashMap. Therefore,
I am going to change the implementation to create a new context every time rather than caching
it in a member field.
> OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release
> -------------------------------------------------------------------------------
>                 Key: CONFIGURATION-465
>                 URL:
>             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
>              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:!default.jspa
For more information on JIRA, see:


View raw message