karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2307) ActiveMQ Karaf commands do not work with Karaf 3
Date Thu, 14 Nov 2013 08:11:22 GMT

    [ https://issues.apache.org/jira/browse/KARAF-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822243#comment-13822243
] 

Christian Schneider commented on KARAF-2307:
--------------------------------------------

I now committed a patch that contains the classes and interfaces at the old location. ActiveMQ
karaf still has the wrong import range for the unchanged parts of the api (org.apache.karaf.shell.console)
though.
We now can either open up the import range for activemq-karaf to include the 3.x versions
of the package or we have to export the package in a 2.x version.

I have tested a patched version of activemq-karaf where I opened the import ranges to [2.3,4).
After this change the activemq feature loads but the commands still do not work. 
[~jbonofre] could you have a look at  this. I think we are not too far from a solution.


> ActiveMQ Karaf commands do not work with Karaf 3
> ------------------------------------------------
>
>                 Key: KARAF-2307
>                 URL: https://issues.apache.org/jira/browse/KARAF-2307
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>    Affects Versions: 3.0.0.RC1
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 3.0.0
>
>         Attachments: amq-4492.patch
>
>
> The ActiveMQ Karaf commands import the package org.apache.felix.gogo.commands.basic which
was exported by karaf shell before version 3.
> I first tried to change the activemq commands like we did for cxf and camel. The problem
is that the activemq commands are quite generic as they simply map the activemq console commands.
So they really need the package above.
> So my aproach is to create the package in karaf shell with deperecated classes extending
the new classes. So this should provide the necessary compat layer. There classes can be removed
once all commands are switched to pure karaf 3.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message