The immediate small issue is that the version range for shell.console
does not include 3.0.0 so it does not even try to install.
I digged a bit deeper and found that the annotations have moved to
another package. The blueprint namespace also changed.
I think it is even more than just namespace changes.
So I am currently investigating if we can provide a compatibility bundle
I am not sure though if it is feasible. As this all will take some time
I think it would make
sense to have the commands as their own feature. This makes us less
dependent on karaf internals anyway. If there is not compat bundle we
can then have two command bundles
one for 3.x and one for 2.x.
I am also working on karaf to create a separate API for karaf commands
so the Karaf community clearly communicates which classes are API and
which are impls.
https://issues.apache.org/jira/browse/KARAF-1427
So we hopefully find a way to keep the API stable for 3.x.
Christian
Am 30.04.2012 11:53, schrieb Claus Ibsen:
On Mon, Apr 30, 2012 at 11:18 AM, Christian Schneider
<ch...@die-schneider.net> wrote:
Hi all,
we provide some camel commands for karaf in our distro. With Karaf 3 there
are some incompatible changes in the command API. So currently camel does
not install on Karaf 3.
I will try to work out a solution for the commands to ideally make them
compatible.
For the moment though I propose we remove the command bundle from the
camel-core feature and move it to a command that can be installed
spearately. So Camel can already be used and tested on Karaf 3. Is this ok?
If yes for what versions of camel should I do this change? I think 2.9.x and
trunk could make sense.
What is the compatibly issue?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
