This question already has an answer here:
Our closed-source proprietary web application uses quite a lot of libraries with different licenses (namely Apache 2.0, MIT, BSD-like, LGPL 2.1, etc). We want to distribute binaries (ear files, specifically) together with these libraries' jars.
If I understand correctly, most of the licenses demand from the distributor to put libraries licenses into the distribution package.
This problem must come up all the time. Is there a standard/canonical way to do this? As I saw in other projects (e.g. PostgreSQL), there does not appear a standard way to specify the list of licenses. Is it sufficient to put somewhere all the licenses and the list of libraries and which library is issued under each license?
UPDATE: In the comments the link to the similar question was posted and if i get it correctly, i need to put library license file and 'NOTICE' file. Is there a standard way of doing it? For example, in PostgreSQL there's one big file for all licenses. Also what should i put in 'NOTICE' file?