Hi Benjamin,
The feature resolver will try to find the feature matching the
requirements, so it's not necessary the "highest" one in the range.
For instance, if you have another feature installing spring-jms 3.2.18,
and then you install your feature containing sring-jms feature with
version range [3.2,5), then this feature won't install the "highest" as
the current installed already matches the version range expectation.
Regards
JB
On 10/06/2016 04:09 PM, Benjamin Graf wrote:
Hello,
I'm actually playing with integrating ActiveMQ Artemis (1.5-SNAPSHOT)
with Camel (2.17.3) on Karaf (4.0.8-SNAPSHOT). To get some conflicts
workarounded I'm deleting jms 1.1 API bundle from camel-jms feature
(2.17.3) and also from latest spring-jms feature (4.2.5.RELEASE_1). But
the jms bundle is still getting resolved and deployed. After some
debugging I recognized that the feature resolution process for *<feature
version='[3.2,5)'>spring-jms</feature>* resolves every possible
spring-jms feature and therefor jms gets resolved from an earlier
version. I was thinking only one (the latest version) gets resolved for
this purpose.
Am I wrong?
Best regards,
Benjamin
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
