[ANNOUNCE] Apache Qpid ProtonJ2 1.0.0-M6 released

2022-05-27 Thread Timothy Bish
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache ProtonJ2 1.0.0-M6. This is the latest release of our AMQP Java client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around

[RESULT][VOTE] Release Apache Qpid ProtonJ2 1.0.0-M6

2022-05-27 Thread Timothy Bish
There were 3 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated after the release has had time to sync to the mirrors and maven central. -- Tim Bish

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M1 (RC1)

2022-05-27 Thread Timothy Bish
On 5/27/22 11:42, Robbie Gemmell wrote: On Thu, 26 May 2022 at 19:57, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M1 Qpid proton-dotnet release, please give it a test out and vote accordingly. This is the first milestone release for this new .NET based

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M1 (RC1)

2022-05-27 Thread Timothy Bish
On 5/26/22 14:57, Timothy Bish wrote: Hi folks, I have put together a release candidate for a 1.0.0-M1 Qpid proton-dotnet release, please give it a test out and vote accordingly. This is the first milestone release for this new .NET based AMQP client and accompanying protocol engine. The

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M1 (RC1)

2022-05-27 Thread Robbie Gemmell
On Thu, 26 May 2022 at 19:57, Timothy Bish wrote: > > Hi folks, > > I have put together a release candidate for a 1.0.0-M1 Qpid > proton-dotnet release, > please give it a test out and vote accordingly. This is the first > milestone release for this > new .NET based AMQP client and accompanying

Re: Tangent on approach to run example (was Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M6)

2022-05-27 Thread Robbie Gemmell
Running "clean package" only builds the jars/archives inside the respective target dirs in the build tree. The component classes/poms of the current maven reactor build are visible within that running build for tests etc, but are not visible outwith it to any others builds, as the seperate/former