If you look in the lib directory of the binary distibution, some libraries don't have an associated license file - either within the JAR itself, or in the lib directory.
There's some related discussion on
WHIRR-100, when we last did this. Basically, every time we add or update a JAR we need to check whether a license file needs adding. It's a manual process, but I don't know a better way.
Trunk is on a different version of jclouds (beta-9b) to the 0.4.0 branch (beta-9), so I suggest that we fix this on trunk and recut 0.4.0. Otherwise we need to do this process twice, and there seem to be quite a few changes to JARs between these two jclouds releases.
Also, the naming of the new jclouds provider JARs makes this harder than before, since before all jclouds JARs had a "jclouds" prefix so we only needed one license file. Now they don't have a "jclouds" prefix (e.g. aws-common-1.0-beta-9b.jar) so it's not clear that they are jclouds related, so we need an accompanying file in lib for each one (as I understand it). We might also consider only shipping the jars for the cloud providers that we currently support.