ppkarwasz commented on issue #4720: URL: https://github.com/apache/eventmesh/issues/4720#issuecomment-1882869993
For libraries that **don't** bundle their dependencies there is some automatic tooling: [`maven-apache-resources`](https://github.com/apache/maven-apache-resources). It contains Velocity templates that generate `META-INF/LICENSE`, `META-INF/NOTICE` and `META-INF/DEPENDENCIES` files. For example the last one in `log4j-core` looks like this: ``` From: 'com.github.luben' - zstd-jni (https://github.com/luben/zstd-jni) com.github.luben:zstd-jni:jar:1.5.5-11 License: BSD 2-Clause License (https://opensource.org/licenses/BSD-2-Clause) From: 'Conversant Engineering' (http://engineering.conversantmedia.com) - com.conversantmedia:disruptor (https://github.com/conversant/disruptor) com.conversantmedia:disruptor:jar:1.2.15 License: The Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) From: 'FasterXML' (http://fasterxml.com) - Woodstox (https://github.com/FasterXML/woodstox) com.fasterxml.woodstox:woodstox-core:bundle:6.5.1 License: The Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) ``` I believe that for projects that bundle their dependencies a similar mechanism could be used. Notice files are more complex (but fortunately uncommon), but license file IMHO could be listed in a file like the example above (and bundled in a single copy). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
