activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Shannon <christopher.l.shan...@gmail.com>
Subject Re: [Discuss] Move camel-activemq component to camel project and deprecate camel plugin for broker
Date Tue, 07 Feb 2017 19:09:08 GMT
+1, it makes sense to me.  I suppose it would be good to hear what Claus
thinks about moving it to see if there would be any potential issues or
reasons not to move it.

On Tue, Feb 7, 2017 at 10:01 AM, Clebert Suconic <clebert.suconic@gmail.com>
wrote:

> +1
>
> That actually makes things a lot clearer to me.
>
>
> On Tue, Feb 7, 2017 at 7:11 AM, Jean-Baptiste Onofré <jb@nanthrax.net>
> wrote:
> > Hi Christian
> >
> > It sounds good to me.
> >
> > Thanks.
> > Regards
> > JB
> >
> > On Feb 7, 2017, 06:38, at 06:38, Christian Schneider <
> chris@die-schneider.net> wrote:
> >>There are some issues supporting the new camel version 2.18.x in
> >>activemq. See
> >>
> >>https://issues.apache.org/jira/browse/AMQ-6585
> >>
> >>In the issue we discussed that it would be better to have the activemq
> >>camel component in the camel project. There is also the question about
> >>the camel plugin for the broker. I do not know any users who use camel
> >>inside the activemq broker. So the proposal here is to deprecate and
> >>remove the plugin at some point.
> >>
> >>If both are removed from activemq source then managing the dependencies
> >>
> >>is a lot easier.
> >>
> >>What do you think?
> >>
> >>Christian
> >>
> >>
> >>--
> >>Christian Schneider
> >>http://www.liquid-reality.de
> >>
> >>Open Source Architect
> >>http://www.talend.com
>
>
>
> --
> Clebert Suconic
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message