[
https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39922
]
Aaron Crickenberger commented on CAMEL-100:
-------------------------------------------
In my case, I'm using these jars in a jboss deployment. So long as I include
each individual camel jar except camel-activemq, things are OK.
Add camel-activemq to camel-spring's pom.xml, and the run "mvn test" for
camel-spring. I couldn't get this to reproduce for camel-core for some reason.
I apologize that this isn't the most direct example, but the stack trace
looks the same.
> Most recent snapshot requires ActiveMQ
> --------------------------------------
>
> Key: CAMEL-100
> URL: https://issues.apache.org/activemq/browse/CAMEL-100
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-activemq
> Affects Versions: 1.1.0
> Reporter: Aaron Crickenberger
> Priority: Minor
>
> This may be moot given the projects' relationship, but it's a recently
> introduced side effect. Before the most recent snapshot, I was able to use
> Camel without any ActiveMQ jar's floating around so long as I never tried to
> use any "activemq:queue:foo" URI's. Now with the most recent snapshot, the
> first time I do something that uses AnnotationTypeCoverterLoader,
> ActiveMQConverter gets loaded, and then causes a NoClassDefFoundError for
> ActiveMQDestination.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
