I think you have to distinguish between two things. 

1) An Apache Release
2) Software using the Apache License

It might be true that using LGPL libraries in an Apache Licensed project 
doesn't immediately hurt, as long as it's not in a Release of an Apache 
project. Right now our "customers" know that by using our software, that they 
won't have to worry about any Copy-Left issues that using our software could 
introduce. 

However if you use an outside Apache project and then start directly using the 
stuff it pulls in, you might in the end be faced with being stuck with a 
copy-left-license. 

And please use official Apache resources as references and not links on 
Stack-Overflow as in the end the Apache ones are the rules that apply for 
Apache Projects, no matter how many people want the Stack Overflow answer to be 
right ;-)

https://www.apache.org/legal/resolved.html

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/paranam
> 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
>

Reply via email to