3 Replies Latest reply on Oct 4, 2017 4:21 AM by Karsten Klein

    Redistribution of Infinispan Server / License Compliance

    Karsten Klein Newbie

      Hi All,


      we are looking into redistributing Infinispan-Server (currently in version 8.6.2.Final) in a commercial context.


      To be able to do this in a compliant fashion, we'd like to better understand the licensing aspects of all integrated open source components and their associated licenses.


      Looking into the downloaded Infinispan-Server archive we found the following details:


      infinispan-server-8.2.6.Final/copyright.txt     (list of names and emails of contributors to infinispan(-server) we assume)

      infinispan-server-8.2.6.Final/LICENSE.txt     (LGPL 2.1 license text, which we regard the license for all Infinispan-Server artifacts and configuration files)

      infinispan-server-8.2.6.Final/docs/licenses   (folder containing license information of the infinispan-server distribution)

      infinispan-server-8.2.6.Final/docs/licenses/licenses.xml     (an xml descriptor with dependency lists and licenses meta data)


      Based on this we performed a deeper analysis. We basically synchronized the information in licenses.xml with the JAR files contained inside the archive.


      We found that there are significant differences and ambiguities between the two sources of information. The result in brief:


      • There are several JARs listed in the XML, which are not included in the distribution.
      • There are several JARs in the distribution, where no license information is associated in the licenses.xml.
      • For some artifacts there is a mismatch between the version in the distribution and the version referred to in the licenses.xml.
      • And for several artifacts there are ambiguities in terms of the effective license.


      I'm very interested in straightening this out. But I think I need a contact with whom I can exchange the detailed results of the analysis and clarify questions. Internally we have very strict policies on the redistribution of open source components and clear ethics to value the open source community effort.


      Did I miss any information that is of relevance for me, that is not part of the distribution? In general there is an ambiguity between plain infinispan artifacts (JARs; Apache License 2.0) and the Infinispan-Server Distribution (ZIP; LGPL 2.1 + subcomponents). In terms of documentation I couldn't find any background on the matter.


      Looking forward for feedback...


      Best regards

        • 1. Re: Redistribution of Infinispan Server / License Compliance
          Tristan Tarrant Master

          Hey Karsten,


          thanks for asking. We have been addressing this in 9.1 onwards but it is not trivial because many components that server depends on also provide incomplete, incorrect or missing license coordinates.

          Infinispan 9.1.1.Final attempts to fix this by providing license information for all components and normalizing licenses (the number of micro-variations is staggering).

          If you would like to help, we would welcome it very much, but please work with either the master (9.2) or 9.1.x branches. We can then backport to any old branches.



          • 2. Re: Redistribution of Infinispan Server / License Compliance
            Karsten Klein Newbie

            Hi Tristan,


            thanks for the quick reply.


            I could also work with the 9.1.x or master branch. I will have a deeper look inside what you have been doing lately. However I will earliest have a chance to do this at Friday.


            In the meantime I have two general questions (that are rather branch independent):


            Is there some documentation that outlines how you approach this and what the goals are with respect to license management? Can you point me to something in this area?


            Under which license do you consider the Infinispan JAR files (prefix 'infinispan-'). If we look into the artefacts we see LGPL 2.1 (e.g. in infinispan-commons.jar). When you follow the project information on GitHub source is under Apache License 2.0 (infinispan/README.md at master · infinispan/infinispan · GitHub). For us, we would regard the content of the binary (the LGPL 2.1) to be the effective license. However we would need to research that for all JAR files. Is there a general hint that I have overseen? Or, can you explain it in one or two sentences?





            PS: here is a list of the Infinispan JARs in the (8.2.6) distribution:





































            • 3. Re: Redistribution of Infinispan Server / License Compliance
              Karsten Klein Newbie

              I'd like to add the following information to my last question:


              When I build the infinispan Artifacts (e.g. infinispan-commons) from the sources I can find the Apache License 2.0 being included in the META-INF folder (META-INF/LICENSE.txt). The license includes a RedHat copyright statement.


              When I however look in to the infinispan-commons JAR contained in the infinispan-server distribution I see also a license included in META-INF/LICENSE.txt. This time however the general LGPL 2.1 without any RedHat specifics.


              When I download the infinispan-commons JAR from Maven Central I again find the LGPL 2.1 without RedHat specifics.


              Could you please enlighten me whether this is intentional or not. What are the backgrounds?


              Again our conclusion is that the effective license is the LGPL.


              Thanks for the clarification...


              Best regards,