[
https://issues.apache.org/jira/browse/KARAF-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438927#comment-13438927
]
Chris Dolan commented on KARAF-1751:
------------------------------------
Another possible solution would be that version="2.2.7" implicitly means
"[2.2.7,2.2.8)" or something more liberal like that. In that case, my
2.2.7.override trick would work.
> Spring feature dependencies specified too tightly
> -------------------------------------------------
>
> Key: KARAF-1751
> URL: https://issues.apache.org/jira/browse/KARAF-1751
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.2.7
> Reporter: Chris Dolan
>
> Karaf 2.2.7 ships with the "http" feature that specifies pax-web 1.0.9. But I
> need fixes in pax-web 1.1.4 (for Jetty 7.6). So, I create my own
> override-features.xml with an "http" feature with version="2.2.7.override"
> with my version of pax-web. However, the spring-web feature (which is
> transitively required by CXF) declares this prereq:
> {code}
> <feature version="2.2.7">http</feature>
> {code}
> where it should be something like "[2.2,2.3)" or "[2,3)". This
> too-tightly-specified version causes both pax-web 1.0.9 and 1.1.4 to be
> loaded into my container, causing lots of problems.
> This is a issue for many of the Spring features. I request that the versions
> be loosened in the features.xml to allow people like me to selectively
> override transitive features.
--
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
