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

jaxb artifacts have incorrect license set in RPM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 8.0.0.GA-CR1, 8.0.0.GA
    • 8.0.0.Beta-CR1
    • RPM
    • None
    • False
    • None
    • False
    • +

      It looks like the license set for jaxb artifacts in RPMs distribution isn't set as it should be. See:

      # Artefact-name:::rpm-package-name:::zip-license:::rpm-license
      
      jaxb-core:::eap8-jaxb-core:::BSD:::CDDL-1.1 or GPLv2 with exceptions
      jaxb-jxc:::eap8-jaxb-jxc:::BSD:::CDDL-1.1 or GPLv2 with exceptions
      jaxb-runtime:::eap8-jaxb-runtime:::BSD:::CDDL-1.1 or GPLv2 with exceptions
      jaxb-xjc:::eap8-jaxb-xjc:::BSD:::CDDL-1.1 or GPLv2 with exceptions
      

      In ZIP these have the Eclipse Distribution License, Version 1.0 license associated, which is then translated into the BSD abbreviation (see this reference).

      Here are links to (hopefully) relevant artifacts on Maven central with their licensing info:

      Only JXC has reference for the Eclipse Distribution License - v 1.0, others just mention BSD.

      Could you please check? I believe that RPM packages should be updated to contain references to the Eclipse Distribution License - v 1.0 as is in ZIP.

            permaine Permaine Cheung
            jstourac@redhat.com Jan Stourac
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: