Search before asking
Feature Request
As is discussed in #4720, the LICENSE and NOTICE files of the EventMesh binary distribution release need to be maintained manually, and for a long time the contents of the files were incomplete and not replenished in time when new dependencies were introduced.
Following the suggestion in #4720 (comment), I implemented generateDistLicense task that automatically generates the LICENSE file and licenses/ directory, and generateDistNotice task that automatically generates the NOTICE file.
They can be run manually, or automatically when the dist task is executed. After #4719 is merged, I'll specify the generateDistLicense task and the generateDistNotice task as dependencies of the dist task.
The licenses generated by the generateDistLicense task are named after the license name, e.g. Apache-2.0.txt. I can also modify it to be named after an artifact, e.g. log4j-core 2.22.1 Apache-2.0.txt. Please let me know if you want to do like that.
Are you willing to submit PR?
Code of Conduct
Search before asking
Feature Request
As is discussed in #4720, the LICENSE and NOTICE files of the EventMesh binary distribution release need to be maintained manually, and for a long time the contents of the files were incomplete and not replenished in time when new dependencies were introduced.
Following the suggestion in #4720 (comment), I implemented
generateDistLicensetask that automatically generates theLICENSEfile andlicenses/directory, andgenerateDistNoticetask that automatically generates theNOTICEfile.They can be run manually, or automatically when the
disttask is executed. After #4719 is merged, I'll specify thegenerateDistLicensetask and thegenerateDistNoticetask as dependencies of thedisttask.The licenses generated by the
generateDistLicensetask are named after the license name, e.g.Apache-2.0.txt. I can also modify it to be named after an artifact, e.g.log4j-core 2.22.1 Apache-2.0.txt. Please let me know if you want to do like that.Are you willing to submit PR?
Code of Conduct