That's a good point, regarding the packaging being separate for Fedora and
as well on other distributions such as RHEL. Once working it may be work
investigating splitting it for MacPorts as well for security as well as
consistency reasons.
On Mon, Oct 2, 2017 at 6:02 AM, Gordon Sim
+1. I used the staged jars and run them against different versions of the
C++ broker (master, 1.36, 1.35 and 0.34). All looks OK.
On Wed, Oct 4, 2017 at 10:12 PM, Gordon Sim wrote:
> On 04/10/17 12:35, Robbie Gemmell wrote:
>
>> I have put together a spin for a 0.26.0 Qpid JMS
On 04/10/17 12:35, Robbie Gemmell wrote:
I have put together a spin for a 0.26.0 Qpid JMS client release, please
give it a test out and vote accordingly.
+1
(Built binary tarball from source including running tests, installed and
ran example against both brokers and the router).
On 4 October 2017 at 12:35, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a 0.26.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
>
On 10/04/2017 07:35 AM, Robbie Gemmell wrote:
Hi folks,
I have put together a spin for a 0.26.0 Qpid JMS client release, please
give it a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.26.0-rc1/
The maven
Hi folks,
I have put together a spin for a 0.26.0 Qpid JMS client release, please
give it a test out and vote accordingly.
The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.26.0-rc1/
The maven artifacts are also staged for now at: