Actually, if you take a look in the Camel features descriptor, Camel
references the CXF feature (with version range):
<features name='camel-${project.version}'>
<repository>mvn:org.apache.cxf.karaf/apache-cxf/${cxf-version}/xml/features</repository>
So, Camel already defines the expected CXF version.
The missing part (resolved in ServiceMix) is ActiveMQ (actually, for
ActiveMQ it's the opposite: ActiveMQ features descriptor references
Camel features).
Regards
JB
On 02/09/2014 12:27 AM, Mike K wrote:
Hi,
How would you resolve dependency versions for main components like Camel
and CXF and AMQ that those are aligned?
Is there any easy way to pick up at will Camel version and CXF version
without thinking of what those use inside?
tnx
Michael.
-----Original Message----- From: Jean-Baptiste Onofré
Sent: Saturday, February 08, 2014 3:12 PM
To: [email protected]
Subject: Re: To servicemix or not to servicemix
Yes, it could like this. We can pre-load some features repositories in
Karaf distribution (using a config file for instance, extending
etc/org.apache.karaf.features.repos.cfg).
Or, it's where Cave could be interesting: Karaf can connect to Cave
repository providing the features.
Regards
JB
On 02/09/2014 12:09 AM, Krzysztof Sobkowiak wrote:
Do you mean, the user should first add the enterprise feature repository
using repo-add command to use the enterprise features (like currently
camel, dosgi, wicket,...)?
On 08.02.2014 23:58, Jean-Baptiste Onofré wrote:
Hi,
Yes, it's what I proposed some time ago: extract the non-core features
from Karaf itself (and not ship them with the distributions), and
provide it as a dedicated sub-project.
I will move forward on this with a formal proposal and branch on github.
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
