+1

I checked things out as follows:
- Verified the signature and checksum files.
- Checked the LICENCE and NOTICE files in the archives.
- Used mvn apache-rat:check to verify licence headers in the source archive.
- Ran the source build and tests.
- Used the staging repo with the Qpid JMS client master build and tests.
- Used the client build in the Qpid Broker-J master build and tests.
- Used the client and Qpid Broker-J master to run the joram tests.
- Used the staging repo with the ActiveMQ Artemis master build and
AMQP tests, inc earlier client build.
- Ran the JMS HelloWorld example against Broker-J, Artemis, and
Dispatch masters.

Robbie

On 13 April 2018 at 20:03, Robbie Gemmell <robbie.gemm...@gmail.com> wrote:
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.27.0 release, please
> test it and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.0-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1136
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342819
>
> Regards,
> Robbie
>
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
>
>   <repositories>
>     <repository>
>       <id>staging</id>
>       
> <url>https://repository.apache.org/content/repositories/orgapacheqpid-1136</url>
>     </repository>
>   </repositories>
>
> The dependency for proton-j would then be:
>
>   <dependency>
>     <groupId>org.apache.qpid</groupId>
>     <artifactId>proton-j</artifactId>
>     <version>0.27.0</version>
>   </dependency>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to