On 15 May 2010 15:04, Rajika Kumarasiri <[email protected]> wrote: > When I first build Qpid java broker and looked inside the bin folder I was > confused. This happens due to the fact there are lot of scripts which I > couldn't figure out what they do by looking at their names. ( Next thing I > did was to check README.txt which really didn't help to figure out what the > scripts does). I suggest we do some re-factoring on these scripts. > 1. Have self descriptive names for the scripts ( so that one can figure out > which scripts to run by seeing the name). For instance which is the first > script to run qpid-run, qpid-server. > 2. Move the utility scripts such as setenv, set_classpath to a util > directory inside bin directory. > 3. Move client/examples scripts to client/examples directory. > 4. Use a consistent naming convention when naming the script. See > topicListener.sh, run_sub.sh, qpid-run etc.. > 5. Add a compressive README.txt if required.
If anyone is doing this, it might be an idea to make some startup scripts that are rc.d compatible, such that they can take start/stop/restart as the first argument, and also store the broker pid in a file? adk. -- -- andrew d kennedy ? edinburgh : +44 7941 197 134 --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
