On 21 June 2017 at 16:10, Keith W <[email protected]> wrote:
> Hi all,
>
> A release candidate for the next release (6.0.8) of the Qpid Java
> Components has been created.
>
> The list of defect fixes can be found in Jira:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.8
>
> Please test and vote accordingly.
>
> The source and binary archives can be grabbed from here:
> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.8-rc1
>
> Those files and the other maven artifacts are also staged for now at:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1110
>
> Kind regards
>
> 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-1110</url>
> </repository>
> </repositories>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
+1
I checked things over as follows:
- Verified all the signatures and checksum files.
-- The .md5 files in the binaries subdir don't contain the associated file
names, so they don't verify as easily with tools. The src .md5 does.
- Checked the LICENCE+NOTICE files present in each archive.
- Used "mvn apache-rat:check" to verify the headers in source release.
- Ran the source release build.
- Started the broker from the tar.gz binary, loaded the web management
console and created a queue to use with client examples.
- Ran the Qpid JMS master HelloWorld example against the running broker.
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
