+1 On 15 April 2016 at 12:54, Keith W <[email protected]> wrote: > Alex/Robbie > > Thanks for spotting the missing signature. It is now fixed. > I have renamed the source artefact too. > > Regarding the src bundle name, the source artefact is being > automatically created by Maven using standard configuration from the > Apache parent pom. It takes the name of the parent module: > qpid-java-build. With hindsight the parent module should not have been > named so, but this is now moot. We could consider a rename of the > parent artefact for v6.1, but this would create a breaking change for > users consuming the qpid-java-build pom artefact. As Robbie points > out we could add a module dedicated to generating a src artefact with > the right name, but this feels like overkill. I've taken the > pragmatic approach for now of tweaking the release instructions to > include the rename step. In the medium term, when the Java Broker is > split from the (legacy) JMS clients in to separate, we can get this > right. > > [1] > https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Java+Components > > On 15 April 2016 at 11:19, Oleksandr Rudyy <[email protected]> wrote: >> I made the following checks: >> 1) Verified pgp signatures against public keys in >> http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there >> and should be appended manually. >> 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site >> generating script(s) expect(s) it to be named qpid-java-6.0.2.tar.gz. >> I am fine with naming it qpid-java-build-6.0.2.tar.gz but we should >> change site scripts. Alternatively, bundle can be renamed manually and >> signatures regenerated >> 3) Started broker and briefly clicked through operations on Web >> Management Console. Everything worked fine for me >> 4) Compiled 6.0.2 artifacts from source bundle. Everything compiled >> successfully >> 5) Run Hello/Spout/Drain examples. >> >> The question is do we want to rename source bundle into >> qpid-java-6.0.2.tar.gz? >> >> Kind Regards, >> Alex >> >> On 13 April 2016 at 14:04, Keith W <[email protected]> wrote: >>> Hi all, >>> >>> A release candidate for the next release (6.0.2) of the Qpid Java >>> Components has been created. >>> >>> The list of changes can be found in Jira: >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.2 >>> >>> 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.2-rc1 >>> >>> Those files and the other maven artifacts are also staged for now at: >>> https://repository.apache.org/content/repositories/orgapacheqpid-1071 >>> >>> 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-1071</url> >>> </repository> >>> </repositories> >>> >>> --------------------------------------------------------------------- >>> 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] >> > > --------------------------------------------------------------------- > 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]
