+1
- built against Proton 0.23 and ran bin/test.sh
- ran messages through a router mesh
- verified stand-alone console runs and shows message flow
- built hawtio console and installed under apache tomcat
- verified hawtio plugin runs
On Fri, May 25, 2018 at 5:45 PM, Ganesh Murthy wrote:
> Hell
+1
* Validated signatures and checksums
* Checked for presence of LICENSE and NOTICE files
* Checked README file
* Ran mvn apache-rat:check, no files with missing license headers found.
* Tried to build against Proton 0.22.0 and made sure that the code wont
compile. This version of Dispatch require
On 24 May 2018 at 12:31, Robbie Gemmell wrote:
> On 23 May 2018 at 20:53, Robbie Gemmell wrote:
>> I have put together a spin for a Qpid Proton 0.23.0 release, please
>> give it a test out and vote accordingly.
>>
>> The source archive can be grabbed from:
>> https://dist.apache.org/repos/dist/de
+1
I checked things out as follows:
- Verified the signature and checksum files.
- Checked for LICENCE+NOTICE files in archive.
- Ran mvn apache-rat:check to verify the licence headers.
- Built the router against an install of Proton 0.23.0 RC1 and ran the tests.
- Ran the JMS client HelloWor
Hello All,
Please cast your vote on this thread to release RC4 as the
official Qpid Dispatch Router version 1.1.0.
RC4 of Qpid Dispatch Router version 1.1.0 can be found here:
https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc4/
The following features, improvements, and bug
https://issues.apache.org/jira/browse/DISPATCH-1012
On Fri, May 25, 2018 at 8:20 AM, Hudalla Kai (INST/ECS4)
wrote:
> I agree, releasing undeliverable messages sounds like the reasonable thing to
> do and would indeed solve our problem.
>
>
> @Ted: can you post the JIRA's URL so that we can trac
I agree, releasing undeliverable messages sounds like the reasonable thing to
do and would indeed solve our problem.
@Ted: can you post the JIRA's URL so that we can track it?
From: Ted Ross
Sent: Thursday, May 24, 2018 5:59:32 PM
To: users@qpid.apache.org
Subj