qpid-cpp is ok on AIX.
> -Original Message-
> From: Justin Ross [mailto:justin.r...@gmail.com]
> Sent: Tuesday, March 10, 2015 9:22 AM
> To: users@qpid.apache.org
> Subject: 0.32 release update - RC is available
>
> Hi, folks. The 0.32 release candidate is now available.
>
> Release a
Justin,
I tested 0.32 RC java broker and java JMS clients by starting the broker
and running Hello/Spout/Drain examples from 0.8/0.9.x/0.10 JMS client and
Hello example from 1.0 JMS client.
They worked fine for me. No issue is found.
Additionally I tested web management console operations like crea
Yes.
> -Original Message-
> From: Michael Ivanov [mailto:iv...@logit-ag.de]
> Sent: Tuesday, March 10, 2015 4:52 PM
> To: users@qpid.apache.org
> Subject: Images transfer
>
> Good evening,
>
> Is it reasonable to use amqp messages (currently I am using proton together
> with qpidd) for i
I've made a fix as https://svn.apache.org/r1665702 on trunk.
The impact of the change is solely to the automatic upgrader, and
specifically only for the path that is currently causing the error
(key/trust stores where the default type was previously being used in
the config).
-- Rob
On 10 March
Good evening,
Is it reasonable to use amqp messages (currently I am using proton together
with qpidd)
for image transfer? The images are expected to be of 1 ... 1.5Mb size.
Best regards,
--
\ / | |
(OvO) | Mikhail Iwanow |
(^^^) | V
Hi Everyone,
FYI, I'm going to be out of contact for a few days again. So far the two
issues discovered in this RC are quite isolated, so please continue to test
RC 1 and make sure any new fixes go on the 0.9 branch. I will spin another
RC off of the branch as soon as I'm back.
Thanks,
--Rafael
- Original Message -
> From: "Rafael Schloming"
> To: users@qpid.apache.org
> Sent: Tuesday, March 10, 2015 6:44:29 AM
> Subject: Re: proton application context API deprecated in 0.9?
>
> On Mon, Mar 9, 2015 at 4:11 PM, Ken Giusti wrote:
>
> > Hi Rafi - thank you for that description.
Hi, folks. The 0.32 release candidate is now available.
Release artifacts: https://dist.apache.org/repos/dist/dev/qpid/0.32-rc/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapacheqpid-1027
Test output: http://people.apache.org/~jross/qpid-0.32-rc.log
This is pr
+1 for option 3
On 9 March 2015 at 16:24, Robbie Gemmell wrote:
> Hi all,
>
> As you probably know, we migrated the Proton and new JMS client code
> to Git repositories last year. As part of the process the old
> locations within the Subversion repo were frozen read-only and left in
> place.
>
>
On Mon, Mar 9, 2015 at 4:11 PM, Ken Giusti wrote:
> Hi Rafi - thank you for that description. I'll have to dig into that code
> a bit more to get a feel for it.
>
> The only concern I have is the implementation of PN_HANDLE. If I'm
> correct, you can't directly share PN_HANDLE's across compilat
On 9 March 2015 at 16:24, Robbie Gemmell wrote:
> Hi all,
>
> As you probably know, we migrated the Proton and new JMS client code
> to Git repositories last year. As part of the process the old
> locations within the Subversion repo were frozen read-only and left in
> place.
>
> Some folks have b
+1 for option 1
-Ursprüngliche Nachricht-
Von: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
Gesendet: Montag, 9. März 2015 17:25
An: users@qpid.apache.org
Betreff: handling old Subversion contents after migrations to Git
Hi all,
As you probably know, we migrated the Proton and new J
12 matches
Mail list logo
