On Thu, Aug 14, 2014 at 10:23 AM, Justin Ross <[email protected]> wrote: > > The Java QMF2 tools and GUI Fraser made will need an archive. They >>> currently live under tools, but are not included in the archive with the >>> other QMF tools. >>> >> >> I'd love to have that included if possible and I would commit to testing >> and voting on it if we are in a position to have a release artefact in time >> for 0.30. >> > > With 0.30 beta, we have the -bin packages from the maven output. The > qpid-tools source archive does also include the java source of Fraser's > tools. > > Based on Gordon's suggestion, here's what I think we would have (with > versions adjusted): > > Source archives, each to be voted independently: > > qpid-cpp-0.30-beta.tar.gz > qpid-java-0.30-beta.tar.gz > qpid-python-0.30-beta.tar.gz > qpid-qmf-0.30-beta.tar.gz > qpid-tests-0.30-beta.tar.gz > qpid-tools-0.30-beta.tar.gz > > Java binaries: > > qpid-java-amqp-1-0-client-jms-0.30-beta-bin.tar.gz > qpid-java-broker-0.30-beta-bin.tar.gz > qpid-java-client-0.30-beta-bin.tar.gz > qpid-broker-plugins-management-qmf2-0.30-beta-bin.tar.gz > qpid-qmf2-tools-0.30-beta-bin.tar.gz > > To be removed: > > qpid-0.30-beta.tar.gz > qpid-wcf-0.30-beta.zip >
Here's a preview of what I've got going. This example run is against trunk, but the same structure would be reflected into 0.30. Note that the dispatch and proton artifacts get removed before doing the "Qpid" release. http://people.apache.org/~jross/quirk/20140819/ http://people.apache.org/~jross/quirk/20140819/java-binaries/ I added qpid-qmf2, Fraser's stuff; I'm thinking about renaming the archive to qpid-java-qmf-tools. Correspondingly, the python tools archive is back to being just python code The java binaries are now precisely the same as "mvn package" generates. These include websocket and perftests binaries that no one has yet expressed a desire for. Justin
