camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-100) Most recent snapshot requires ActiveMQ
Date Tue, 04 Sep 2007 10:06:22 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Strachan resolved CAMEL-100.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

I figured out how to make this test case actually fail in the end; then added a fix for it.

> 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
>             Fix For: 1.2.0
>
>
> 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.


Mime
View raw message