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 pro
On Mon, Apr 30, 2012 at 11:18 AM, Christian Schneider
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 co
Some gogo packages have migrated inside Karaf.
On Mon, Apr 30, 2012 at 12:53 PM, Claus Ibsen wrote:
> On Mon, Apr 30, 2012 at 11:18 AM, Christian Schneider
> wrote:
> > Hi all,
> >
> > we provide some camel commands for karaf in our distro. With Karaf 3
> there
> > are some incompatible changes
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 c
Hi,
For the others, the incompatible stuff are:
- the version range in the OSGi import statement (it should be something
like [2.2,4) instead of [2.2,3)
- in Karaf 3.0 (trunk), we moved some packages from gogo to karaf, and
so the import statement should be improved
On the other hand, in Kara
It could easy for us to break the dependency of karaf 2.2.x when the
karaf 3.x is out.
I don't think the define gogo and karaf import as optional can make the
camel command
support the karaf 2.2.x and karaf 3.x at the same time, if the user
still want to use the camel command.
On Mon Apr 30 19
