Martin Ritchie wrote:
Thanks for everyone's input on this:Seems like we are all agreeing that more discreet packages would be better. Just to summerise what everyone has said I believe these packages is what everyone is looking for: A single source package for the source release as well as the cpp source package that removes the build dependency on ruby. The provided binaries would be split in to broker, client, examples and tools. The C++ binaries that we actually build could be limited to Windows, as downstream packagers will provide other builds we can link to. Each client language should have their own package and an additional example/documentation package. Finally we will have a set of packages for the management tools from all languages. Carl, you mentioned other C++ tools but on the wiki I only see details about QMF and QMan if you let me know what the other items that we should package are I'll pop them on the list here: - Single Source package - C++ Source package - Binary Packages for + Brokers + C++ - Windows only from Qpid, simply link to other downstream binary builds for other platforms + Java + Client and Example Package + C++ - Windows only from Qpid, simply link to other downstream binary builds for other platforms + C# (0-8,0-10) + Java + Python + Ruby + Management - Eclipse JMX Console + Win + Linux + OS X - JMX Command Line Tool - QMan / WsDmAdapter
The QMF command line tools are missing from the list Carl. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
