On 2 August 2017 at 15:33, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > Hi folks, > > I have put together a first spin for a Qpid Proton-J 0.20.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.20.0-rc1/ > > (Note: the .sha checksum files are generated using SHA512) > > The maven artifacts are staged for now at: > https://repository.apache.org/content/repositories/orgapacheqpid-1111 > > The JIRAs currently assigned are: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12341280 > > 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-1111</url> > </repository> > </repositories> > > The dependency for proton-j would then be: > > <dependency> > <groupId>org.apache.qpid</groupId> > <artifactId>proton-j</artifactId> > <version>0.20.0</version> > </dependency>
Adding my +1. I checked things over as follows: - Verified the signatures and checksum files. - Checked the LICENCE and NOTICE files in the release archives. - Ran the source build and tests. - Used mvn apache-rat:check to verify the source release licence headers. - Checked the bin convenience archive contained the expected bits. - Used the staging repo to run the Qpid JMS client master build and tests. - Used the staging repo to run the ActiveMQ 5 master build and AMQP tests. - Ran the JMS client HelloWorld example against Qpid Broker-J 6.1.4 and and ActiveMQ 5 master brokers. Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
