[
https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40062
]
James Strachan commented on CAMEL-100:
--------------------------------------
I've added a test case to try reproduce this issue...
https://svn.apache.org/repos/asf/activemq/camel/trunk/tests/camel-partial-classpath-test/
am using a custom type converter, adding camel-activemq to the classpath but
(AFAIK) without ActiveMQ and its working without any errors.
Maybe this has been fixed; or maybe I'm just not doing the right thing to
reproduce your issue? Any ideas how to reproduce it? e.g. an example classpath
that causes problems maybe?
> 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.
