Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37010

Modules licenses for JS libs are not included in standard HPI

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • js-builder, js-modules
    • 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...

          [JENKINS-37010] Modules licenses for JS libs are not included in standard HPI

          Tom FENNELLY added a comment -

          For CJE etc, why not just look at what it depends on and add the licences by hand? I don't think there are that many deps.

          Tom FENNELLY added a comment - For CJE etc, why not just look at what it depends on and add the licences by hand? I don't think there are that many deps.

            tfennelly Tom FENNELLY
            kzantow Keith Zantow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: