camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <>
Subject [jira] [Reopened] (CAMEL-10367) remove extraneous dependency from camel-amqp module
Date Fri, 07 Oct 2016 11:08:20 GMT


Robbie Gemmell reopened CAMEL-10367:

[~davsclaus] thanks for merging, I've closed the PR as requested. You can close PRs agaisnt
the mirrors yourself by including "This closes #<pr-number>" in a commit log, e.g either
using a merge commit or even editing the original. I beleive they close themselves without
any message if merged while the commit would become the new head without any rebasing.

I see the fix version was updated to 2.19.0 presumably as 2.18.x had already branched, which
I hadn't spotted until now, and was later started on a vote for release. Master is still versioned
2.18.0-SNAPSHOT however, can it be updated to avoid confusion? 

Any comments on the other related questions I asked? Once those are answered perhaps this
could then be backported.

> remove extraneous dependency from camel-amqp module
> ---------------------------------------------------
>                 Key: CAMEL-10367
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-amqp
>    Affects Versions: 2.17.3
>            Reporter: Robbie Gemmell
>            Assignee: Claus Ibsen
>             Fix For: 2.19.0
> I notice from that camel-amqp is considered to support
only AMQP 1.0 as of Camel 2.17.0. The camel-amqp module however in addition to its dependency
on the newer Qpid AMQP 1.0 JMS client, continues to have a dependency on an old version of
the Qpid AMQP 0-x JMS client. Since it isn't used anymore this dependency should be removed.

This message was sent by Atlassian JIRA

View raw message