The best place to look is available directly from IBM. See this answer for the different versions of the available Java / JMS WMQ client.
As for the best way to package them, remember that if you want IBM to support them, you need to install client code, not just link the jar files. The reason IBM is reluctant to support custom installations should also concern you if the application should be installed in Production. The full client includes significant additional features such as diagnostics, trace functions, crypto libraries, JSSE, etc. In addition, this is the only installation with which you can use the IBM service.
If you install banks from a third-party site, for example, linked above, do you know which version? Has any service been applied? Have the latest fixes been applied? Since IBM only distributes the full client, and OEMs do not have the right to distribute jar files other than as part of their application, any site offering WMQ jar files will, by definition, pirate them.
I understand that requiring you to fully install the client is considered burdensome when you are used to just grabbing some banks and going. On the other hand, if you do not need support, you can install the WMQ client on a virtual machine somewhere, keep it up to date and take jar files from it. Thus, you have a well-known set of files, all of which are synchronized and to which you can apply maintenance .
If you want to offer IBM that they need a lighter Java solution, feel free to raise a requirement (or vote for it if it already exists) in the IBM Community for Improvement (RFE) .
T.Rob source share