Hi all,

Now that we have entered another release phase I think it would be a good time 
to discuss the release artifacts. I would like to see 0.6 ship with some 
updates to the artifacts we produce to make things more useful and obvious for 
our users. 

The "Java broker, client, and tools" multi-component package appears to be just 
a copy of the etc/ lib/ and bin/ directories from the qpid/java/build/ dir 
after performing a build and this makes it quite messy. A lot of test 
configuration files are left in the etc/ dir and there are loads of jars in the 
lib/ dir, which make it very hard to know which is being used where or allow 
splitting them up easily. You also end up with jars that just aren't intended 
to be used from there (eg the eclipse-plugin used in the JMX Management Console 
releases). We have single component packages for the Java broker, client, and 
management tools so if we want a multi-component package including any of these 
I think we should simply bundle those up instead of just tarring the build 
folder and mashing everything together. 

Another result of the above is that QMan is shipped in the Java multi-component 
bundle despite the fact it is only useful if you have a C++ broker. I realise 
it is written in Java, but those packages don't seem to me like they should 
necessarily be language specific. If anything I would say that QMan should 
surely ship in the multi-component bundle along with the items it can actually 
be used with (ie the C++ broker and client bundle), or just be made available 
standalone (which it already is). Users aren't necessarily going to expect they 
need to download both multi-component packages to make use of everything 
contained in one of them, and as mentioned above, splitting QMan alone out of 
the java multi-component bundle would be a bit hideous and non obvious anyway.

I would also like to see us tagging the source-only release artifacts with 
'src', ie the C++ and the "full" release artifact that is just a copy of the 
entire repo. It isn't exactly helpful for a user to download the 50MB file then 
find out what they are looking for isn't actually in there.

Robbie


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Reply via email to