You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rich Mayfield (Created) (JIRA)" <ji...@apache.org> on 2011/10/03 19:29:34 UTC
[jira] [Created] (CONFIGURATION-465) commons-configuration
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
[jira] [Commented] (CONFIGURATION-465) OSGI issue - configuration
depends on Jexl 1.0 which does not have OSGI release
Posted by "Oliver Heger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190475#comment-13190475 ]
Oliver Heger commented on CONFIGURATION-465:
--------------------------------------------
As configuration 1.8 will target Java 1.5, it is possible to switch to a Jexl 2.x version. AIUI this should solve this problem.
I committed a change which sets the Jexl version to the most recent 2.1.1. A few adjustments in {{ExprLookup}} were necessary. Ralph, can you have a short review whether may changes are correct (I am not familar with Jexl)? The unit test is still green.
> OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release
> -------------------------------------------------------------------------------
>
> 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
[jira] [Updated] (CONFIGURATION-465) OSGI issue - configuration
depends on Jexl 1.0 which does not have OSGI release
Posted by "Sebb (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb updated CONFIGURATION-465:
-------------------------------
Summary: OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release (was: commons-configuration )
> OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release
> -------------------------------------------------------------------------------
>
> 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
[jira] [Resolved] (CONFIGURATION-465) OSGI issue - configuration
depends on Jexl 1.0 which does not have OSGI release
Posted by "Oliver Heger (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-465.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.8
Switched to version 2.1.1 of Commons Jexl. This dependency should be resolvable in an OSGi environment.
> OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release
> -------------------------------------------------------------------------------
>
> 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
> Fix For: 1.8
>
>
> 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
[jira] [Commented] (CONFIGURATION-465) commons-configuration
Posted by "Rich Mayfield (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CONFIGURATION-465) commons-configuration
Posted by "Rich Mayfield (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120035#comment-13120035 ]
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: 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
[jira] [Commented] (CONFIGURATION-465) commons-configuration
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CONFIGURATION-465) OSGI issue - configuration
depends on Jexl 1.0 which does not have OSGI release
Posted by "Oliver Heger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190697#comment-13190697 ]
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: 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
[jira] [Commented] (CONFIGURATION-465) OSGI issue - configuration
depends on Jexl 1.0 which does not have OSGI release
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190624#comment-13190624 ]
Ralph Goers commented on CONFIGURATION-465:
-------------------------------------------
As far as I can tell the changes look OK, assuming JexlEngine is thread-safe. If the unit tests are passing then these chagnes should be OK.
> OSGI issue - configuration depends on Jexl 1.0 which does not have OSGI release
> -------------------------------------------------------------------------------
>
> 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