I think he means: Adding a dependency in a pom. It's technically not included in the Apache release. However if you build something with it, the end product will have to contain it. (A sort of borderline case is if it's used for testing, but isn't included in the final output, but that's a slippery slope).
So in the end if someone would be building something with our Apache licensed library, in the end he would be stuck with something that's technically LGPL ... that's why we don't like that license. Chris -----Ursprüngliche Nachricht----- Von: Jean-Baptiste Onofre <[email protected]> Gesendet: Donnerstag, 2. September 2021 18:23 An: [email protected] Betreff: Re: Apache Wayang dependencies with other licenses What do you mean by « linking » ? You mean use it as dependency ? Regards JB > Le 2 sept. 2021 à 18:21, Alexander Alten <[email protected]> a écrit : > > Thats right, but linking per pom.xml is not an issue, isn’t? > > —Alex > >> On 2. Sep 2021, at 18:18, Christofer Dutz <[email protected]> wrote: >> >> Hi Alex, >> >> unfortunately this is not quite correct. Having LGPL2 is actually something >> we are not allowed to use. >> >> Chris >> >> -----Ursprüngliche Nachricht----- >> Von: Alexander Alten <[email protected]> >> Gesendet: Donnerstag, 2. September 2021 08:25 >> An: [email protected] >> Betreff: Re: Apache Wayang dependencies with other licenses >> >> Hi folks, >> >> According to >> https://opensource.stackexchange.com/questions/5664/linking-from-lgpl >> -2-1-software-to-apache-2-0-library/5756#5756 >> >> the linking to LGPL2 libs is not problematic, the permissive part applies. >> In general the use of other libs, which are not distributed over the >> project, is fine. We just need to make sure that we reference the library in >> the pom.xml file and not distribute them directly. >> BSD license, as well as MIT are compatible. >> >> Chris, and mentors - any comments here before we start to draft the first >> release? >> >> Best, >> --alex >> >> -- >> Alexander Alten >> PPMC Apache Wayang >> >> >> >> On Tue, Aug 31, 2021, 23:57 Rodrigo Pardo Meza >> <[email protected]> >> wrote: >> >>> Hi folks, >>> >>> @bertty contreras <[email protected]> and I have been >>> working on the first release. To this end: >>> >>> (1) We checked the maintenance state of the libraries actively used >>> by Wayang. One of them (HPI) has been deleted and Experiments >>> storage functionalities have been incorporated into the code of >>> Wayang in order to extend them. >>> >>> (2) We checked the licenses of the libraries currently used by Wayang. >>> Not going further to the licenses of the dependencies of these >>> libraries (Only was checked the first level of the dependency tree >>> of Wayang). We found the next observations: >>> >>> - trove4j >>> <https://mvnrepository.com/artifact/net.sf.trove4j/trove4j> >>> has LGPL 2.1 license >>> - antlr4 >>> <https://mvnrepository.com/artifact/org.antlr/antlr4-runtime> >>> has BSD license >>> - paranamer >>> <https://mvnrepository.com/artifact/com.thoughtworks.paranamer/paran >>> am >>> er> has BSD licence. Spark has this dependency as well with runtime >>> scope, if Wayang does the same should be ok? >>> - hsqldb <https://mvnrepository.com/artifact/org.hsqldb/hsqldb> has >>> BSD license >>> >>> Someone can help us to find out if our project can use these >>> dependencies; otherwise, does anyone have suggestions of libraries >>> to replace them? >>> >>> Thanks in advance. >>> >>> Best regards >>> >
