[
https://issues.apache.org/jira/browse/AMQ-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642883#comment-13642883
]
Christian Schneider commented on AMQ-4492:
------------------------------------------
The package org.apache.felix.gogo.commands has been renamed in apache karaf 3
and should better not be used from other projects anyway.
The good news is that there is a way of defining commands that works in karaf
2.x and karaf 3. This is already implemented in current camel and cxf versions.
So the idea is to do a similar change in activemq.
I can prepare a patch for this.
> ActiveMQ does not work on Karaf 3
> ---------------------------------
>
> Key: AMQ-4492
> URL: https://issues.apache.org/jira/browse/AMQ-4492
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.8.0
> Environment: Karaf 3.0.0.RC1
> Reporter: Christian Schneider
> Fix For: 5.9.0
>
>
> when I try to install activemq 5.7.0 into karaf 3.0.0.RC1 I get the following
> error:
> karaf@root()> feature:install activemq-blueprint
> Error executing command: Could not start bundle
> mvn:org.apache.activemq/activemq-karaf/5.7.0 in feature(s) activemq-5.7.0:
> Unresolved constraint in bundle activemq-karaf [297]: Unable to resolve
> 297.0: missing requirement [297.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.felix.gogo.commands.basic)(version>=0.10.0)(!(version>=1.0.0)))
> The exported packages in karaf look like this:
> exports | grep gogo
> org.apache.felix.gogo.api | 0.10.0 | 48 |
> org.apache.karaf.shell.console
> org.apache.felix.gogo.commands | 0.10.0 | 48 |
> org.apache.karaf.shell.console
> org.apache.felix.gogo.runtime.activator | 0.10.0 | 48 |
> org.apache.karaf.shell.console
> org.apache.felix.gogo.runtime.threadio | 0.10.0 | 48 |
> org.apache.karaf.shell.console
> org.apache.felix.gogo.runtime | 0.10.0 | 48 |
> org.apache.karaf.shell.console
> For ActiveMQ 5.8.0 the error is similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
