commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Mayfield (Commented) (JIRA)" <>
Subject [jira] [Commented] (CONFIGURATION-465) commons-configuration
Date Tue, 04 Oct 2011 12:39:35 GMT


Rich Mayfield commented on CONFIGURATION-465:

I guess I should add, and I hinted at this in the defect submission: Even if you do make that
package optional the use of ExprLookup will be dependent upon a new release of Jexl 1.x that
includes the OSGi MANIFEST.MF headers to export packages.

If the Jexl project does not plan to update it's 1.x distribution perhaps someone might "bundle-ize"
the 1.x distribution and make it available via the SpringSource Bundle Repository.

At the very least though making it optional will allow anyone not using Jexl to leverage the
new version of commons-configuration in an OSGi environment.
> commons-configuration 
> ----------------------
>                 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