FYI, Gentoo ebuilds for this release (together with required Proton
versions) are available here:
https://github.com/fourceu/qpid-portage-overlay
On 4 April 2018 at 00:20, Justin Ross wrote:
> The Apache Qpid community is pleased to announce the immediate availability
> of Apache Qpid C++ 1.38.
The Apache Qpid community is pleased to announce the immediate availability
of Apache Qpid C++ 1.38.0.
Apache Qpid (https://qpid.apache.org) is a cross-platform messaging solution
that implements the Advanced Message Queuing Protocol (AMQP,
https://www.amqp.org). It provides message brokers writte
+1
I performed the following tests:
* verified signatures and checksums
* built and ran java-mms.0-9 tests from source bundle
* started broker on fedora 27
* created test queue using Web Management Console
* ran "hello world" example using JMS AMQP 1.0 client
* ran "hello world" example using JMS
+1
I performed the following tests:
* verified signatures and checksums
* built and ran java-mms.1-0 tests from source bundle
* started broker on fedora 27
* created test queue using Web Management Console
* ran "hello world" example using JMS AMQP 1.0 client
* ran "hello world" example using JMS
Since the release of Qpid Proton 0.22.0, Qpid Dispatch Router's tests
fail against the latest released Proton because of the removal of the
deprecated Messenger API. We are planning to push some of the
in-progress Jiras to the next release so we can produce version 1.1.0
soon.
Please look for a r
On Tue, 2018-04-03 at 10:56 +0100, Keith W wrote:
> ...
> Thanks for the replies. The 7.3 Maipo image in question is
> corporatised by our organisation, so it could be special in this
> respect.
"corporatised" sounds like an archaic swear word!
A
---
+1.
My testing was:
1) Verified the sha512 checksums on all distribution artefacts
2) Verified signatures on all the distribution artefacts
3) Ran apache RAT
4) Built/ran test profile bdb (0-9) and dby (0-10) from source bundle
5) Ran hello world against staged maven client artefacts against
brok
On 3 April 2018 at 10:31, Robbie Gemmell wrote:
> "The package is not listed as required in INSTALL.md, I am curious
> whether the instructions needs to be amended to include this package."
>
> It seems its a dependency of the "gcc-c++" package which is mentioned,
> so I'd guess thats why it isnt
"The package is not listed as required in INSTALL.md, I am curious
whether the instructions needs to be amended to include this package."
It seems its a dependency of the "gcc-c++" package which is mentioned,
so I'd guess thats why it isnt noted explicitly. Not sure how you came
to have the x64 ve
Hi Andrew,
Thanks for helping with the issue.
Yes, you are right we are trying to compile for 64 bits.
It is a freshly built Red Hat Enterprise Linux Server release 7.3.
All required dependencies have been installed as per instructions in
proton INSTALL.md [1].
I am not sure how we ended-up wi
+1.
My testing was:
1) Verified the md5/sha checksums on all distribution artefacts
2) Verified signatures on all the distribution artefacts
3) Ran apache RAT
4) Built/ran test profile mms/bdb 0-9/0-10//1.0 from source bundle
(Qpid JMS Client 0.31.0)
5) Generally kicked the tyres within the Web M
11 matches
Mail list logo
