Fork me on GitHub
#clojure
<
2021-09-04
>
borkdude15:09:38

@ericdallo and I are considering using javaparser (a library) in clj-kondo so we can better navigate to classes/methods and find arity errors when calling methods, etc. But this library is LGPL, while clj-kondo is EPL1.0. What should we watch out for?

borkdude16:09:36

Perhaps we can also post this question on ClojureVerse

ericdallo00:09:45

> But if your program simply uses the library, there’s no need to share your source code for your part of the program. You could even make your part of the program proprietary if you wanted to. This looks more detailed: https://fossa.com/blog/open-source-software-licenses-101-lgpl-license/

ericdallo00:09:32

AFAICS I see no problem using a LGPL library on EPL1 project for our case

borkdude09:09:06

> for statically linked libraries, a distributor must offer access to not only the library’s source code, but other information or materials necessary to rebuild the program.

borkdude09:09:10

I guess we're safe then

👍 2
borkdude08:09:22

Ah, you can use javaparser under Apache as well

borkdude08:09:54

and completions

ericdallo12:09:59

That seems a good alternative

Asko Nōmm17:09:43

Can I leverage Clojure CLR to create native binaries? (as opposed to doing it with GraalVM, with regular Clojure).

Asko Nōmm21:09:37

Oh awesome this will do just fine! Thank you @U04V15CAJ