[
https://issues.apache.org/jira/browse/AMQ-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878301#comment-15878301
]
Christopher L. Shannon edited comment on AMQ-6597 at 2/22/17 3:39 PM:
----------------------------------------------------------------------
[[email protected]], I think this patch may be causing unit test issues
in the 5.14.x build.
https://builds.apache.org/view/All/job/ActiveMQ-Java8-5.14.x/31/org.apache.activemq$activemq-karaf-itest/
Can you take a look? It might just be an issue with the Jenkins environment as
I ran the tests locally and they seem to pass.
was (Author: christopher.l.shannon):
[[email protected]], I think this patch may be causing unit test issues
in the 5.14.x build.
https://builds.apache.org/view/All/job/ActiveMQ-Java8-5.14.x/lastBuild/org.apache.activemq$activemq-karaf-itest/testReport/
Can you take a look? It might just be an issue with the Jenkins environment as
I ran the tests locally and they seem to pass.
> activemq-camel does not work together with camel 2.18
> -----------------------------------------------------
>
> Key: AMQ-6597
> URL: https://issues.apache.org/jira/browse/AMQ-6597
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-camel
> Affects Versions: 5.13.5, 5.14.3
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 5.x, 5.13.6, 5.15.0, 5.14.4
>
>
> Start apache karaf 4.1.0 and execute these commands in the console:
> feature:repo-add activemq 5.14.3
> feature:repo-add spring-legacy 4.1.0
> feature:repo-add camel 2.18.2
> feature:install activemq-broker activemq-camel
> The activemq-camel bundle sometimes does not resolve and we get a Uses
> constraint violation error:
> http://apaste.info/3GSjx
> I then deploy this blueprint into the deploy folder: http://apaste.info/i3Uhc
> Strangely when I use the
> org.apache.activemq.camel.component.ActiveMQComponent in a blueprint I get a
> strange error like below
> http://apaste.info/d3f4s
> This might be a dynamic package import thing again. Not sure though.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
