Uploaded image for project: 'Edgent'
  1. Edgent
  2. EDGENT-133

Ensure correct LICENCE and NOTICE are in Quarks jar files

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • Important

    Description

      Currently the top-level LICENSE and NOTICE files are copied into each Quarks file.

      Currently that is the correct behaviour, however as the LICENSE and NOTICE files are changed to represent the contents of the entire source tree that will no longer be correct.

      From the guiding principle [1] "The LICENSE and NOTICE files must exactly represent the contents of the distribution they reside in".

      Any jar created by the build (e.g. target/java8/lib/quarks.api.optlet.jar) is itself a distribution, so its LICENSE & NOTICE must exactly represent its contents. As [2] says: "As far as LICENSE and NOTICE are concerned, only bundled bits matter."

      So, any Java jar currently produced only includes Quarks class files, dependent jars are not bundled in the Quarks jar, so their LICENCE is ALV2. For the NOTICE file there are two choices:
      1) The current NOTICE file containing IBM copyrights and Apache Quarks info but no third-party dependency. Jars that contain any (IBM) code that existed at the time the repo was first populated at the ASF.
      2) A NOTICE file containing Apache Quarks info but no third-party dependency. This would be for jars that only contain code created since the project repo was at the ASF (which most likely means jars created since then).

      • I believe it is all Quarks jar, but it will need to verified as thw work proceeds.

      [1] http://www.apache.org/dev/licensing-howto.html#guiding-principle
      [2] http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled

      Attachments

        Issue Links

          Activity

            People

              dlaboss Dale LaBossiere
              djd Daniel John Debrunner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: