On 5 September 2016 at 16:47, Robbie Gemmell <[email protected]> wrote: > Hi folks, > > I have put together a spin for a 0.11.0 Qpid JMS client release, please > test it and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/jms/0.11.0-rc1/ > > Those files and the other maven artifacts are also staged for now at: > https://repository.apache.org/content/repositories/orgapacheqpid-1085 > > Regards, > Robbie > > > P.S. If you want to test it out using maven (e.g with the examples src, > or your own things), 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-1085</url> > </repository> > </repositories> > > The dependency for the client itself would then be: > > <dependency> > <groupId>org.apache.qpid</groupId> > <artifactId>qpid-jms-client</artifactId> > <version>0.11.0</version> > </dependency>
Adding my +1. I checked things out as follows: - Verified the checksums and signatures. - Checked LICENCE+NOTICE files present. - Checked licence headers with mvn apache-rat:check. - Ran the build and tests from the source archive, no issues. - Used the staging repo with maven to build/run examples from the bin archive against Dispatch, Java broker, C++ broker, and ActiveMQ 5. - Built/run the examples source in the bin archive manually using javac. - Used the staging repo to run the ActiveMQ 5 master build and AMQP tests which use the client. Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
