Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9521

(7.0.z) Enhance the way licenses are presented and fix inconsistencies

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • 7.0.0.GA
    • Build System
    • None
    • EAP 7.0.6

      We need to provide a better view of the existing license information presented in the docs/licenses.xml file, in the form of a docs/licenses.html file that lists:

      Group/Artifact/Version/License (name+original URL)/Local Copy(relative pathname link to local copy of the license in the licenses dir).

      This can be achieved with an .xslt transformation that runs as part of the build process, which produces the desired licenses.html, and it would allow us to zip and forward the entire doc/licenses directory to a client that wants to evaluate the licenses used in EAP.

      In addition we need to sanitize a bit the presented licensing information:

      • License Names should adhere to the standard presented here: https://spdx.org/licenses/ (full license name). Apparently we present the same license using different names which can be confusing, e.g. The Apache Software License, Version 2.0, Apache Software License, Version 2.0, Apache License, Version 2.0, Apache 2, ASL 2.0 all refer essentially to Apache License 2.0
      • The ActiveMQ package misses license name information, it should probably be Apache License 2.0.
      • relaxngDatatype misses full license info
      • Again, we shouldn't list simply "lgpl"

      Some example is attached on the JIRA.

      (Refer to https://issues.jboss.org/browse/JBEAP-9520 for an up to date description.)

            psotirop@redhat.com Panagiotis Sotiropoulos
            dandread1@redhat.com Dimitrios Andreadis
            Peter Mackay Peter Mackay
            Peter Mackay Peter Mackay
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: