+1 ... I used the staged artefacts and run my tests against the C++ broker.
On Tue, Jan 17, 2017 at 2:20 PM, Robbie Gemmell <[email protected]> wrote: > On 16 January 2017 at 18:38, Robbie Gemmell <[email protected]> > wrote: > > Hi folks, > > > > I have put together a spin for a 0.20.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.20.0-rc1/ > > > > Those files and the other maven artifacts are also staged for now at: > > https://repository.apache.org/content/repositories/orgapacheqpid-1097 > > > > 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-1097</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.20.0</version> > > </dependency> > > Making my +1 explicit > > I tested things out as follows: > - Verified the checksum and signature files. > - Checked LICENCE+NOTICE files present/correct. > - Ran mvn apache-rat:check to verify licence headers. > - Ran the build+tests from the source release archive, no issues. > - Built the examples from the binary release archive using maven and > ran against Qpid Dispatch master, Qpid CPP master (both built against > Qpid Proton master), Qpid for Java master, ActiveMQ 5 master, and > ActiveMQ Artemis master. > - Built the examples using javac manually and run to verify required > libs included in lib dir. > - Ran the Joram JMS tests against the Qpid for Java master using the > staging repo. > - Ran the ActiveMQ 5 master tests using the staging repo. > > Robbie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
