+1 Using artefacts from staging, I: - Ran Joram test suite suite against Java Broker (trunk) - Ran the examples
On 8 April 2016 at 14:42, Robbie Gemmell <[email protected]> wrote: > On 7 April 2016 at 18:04, Robbie Gemmell <[email protected]> wrote: >> Hi folks, >> >> I have put together a spin for a 0.9.0 Qpid JMS client release, please >> test it and vote accordingly. >> >> The source and binary archives can be grabbed from here: >> https://dist.apache.org/repos/dist/dev/qpid/jms/0.9.0-rc1/ >> >> Those files and the other maven artifacts are also staged for now at: >> https://repository.apache.org/content/repositories/orgapacheqpid-1069 >> >> 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-1069</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.9.0</version> >> </dependency> > > Making my +1 explicit. > > I tested things out as follows: > - Verified the sigs and checksums. > - Checked LICENCE+NOTICE files present. > - Ran the build and tests from source archive. > - Checked licence headers with mvn apache-rat:check. > - Used the staging repo artifacts to run the examples from the bin > archive, against trunk/master builds of the Qpid C++ broker, ActiveMQ > 5 broker, plus the 6.0.x Qpid Java broker. > - Used the libs from the bin archive to compile the examples and run > against trunk/master build of the Qpid C++ broker. > - Used the staging repo to run the ActiveMQ 5 master build and AMQP tests. > > Robbie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
