-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
To remain consistent with other Jenkins plugins, those that use js-builder should include appropriate license information for included JS files.
NOTES:
I've figured out a basic way to gather this information using the NPM module browserify-licenses. Although it doesn't take into account extDependencies. Just run a script on the source file, e.g. "scripts": { ... "show-licenses": "brlicenses src/main/js/main.js". Other formats are available for this.
It may work to add that as a dependency to js-builder, then add a gulp target to do that, and modify the pom to have it run at the right phase of the HPI build, it might do the trick, more investigation is required...
- blocks
-
JENKINS-35776 Bundle all licenses in the license directory and display them on /legal
- Open
- links to