+1 * checked sha1 checksums * ran the joram test suite against the Qpid Broker for Java
One comment. The checksums do not contain the filenames so you cannot run "sha1sum -c file.sha1". IIRC, this is a shortcoming in the maven plugin. when doing Qpid for Java releases we have a script that fixes the checksum files. See 10.f of https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Java+Components#ReleasingQpidJavaComponents-Major/Minorversionrelease
Kind regards, Lorenz On 08/12/16 17:26, Robbie Gemmell wrote:
Hi folks, I have put together a first spin for a 0.16.0 Qpid Proton release, please test it and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.16.0-rc1/ The maven artifacts for proton-j are staged for now at: https://repository.apache.org/content/repositories/orgapacheqpid-1094 The JIRAs currently assigned are: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12338399 It is tagged as 0.16.0-rc1 from the 0.16.x branch. Regards, Robbie P.S. If you want to test things out using maven (e.g 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-1094</url> </repository> </repositories> The dependency for proton-j would then be: <dependency> <groupId>org.apache.qpid</groupId> <artifactId>proton-j</artifactId> <version>0.16.0</version> </dependency> --------------------------------------------------------------------- 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]
