This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-22
Channels
- # announcements (1)
- # aws (11)
- # babashka (10)
- # beginners (49)
- # calva (32)
- # cljsrn (3)
- # clojure (123)
- # clojure-australia (1)
- # clojure-dev (2)
- # clojure-europe (27)
- # clojure-spec (1)
- # clojurescript (22)
- # clojutre (1)
- # code-reviews (1)
- # conjure (3)
- # editors (32)
- # emacs (3)
- # graalvm (12)
- # kaocha (1)
- # lsp (1)
- # malli (2)
- # off-topic (1)
- # schema (2)
- # shadow-cljs (32)
- # spacemacs (6)
- # tools-deps (4)
The helidon oracle jdbc driver is Apache 2.0. This should be good to use in a native binary that is re-distributed right? Or should I worry about the helidon driver using the proprietary driver inside?
I'm not sure if Oracle is violating their own licenses there, but I don't care, as long as I can use it ;)
@borkdude it's fine, but you need to include a copy of the licence and NOTICE file somewhere. Presumably under -v
, --license
or similar.
@borkdude Hmm, in java this is easy, we just include in the uberjar a copy of all files required. Interesting answer from how GPLv3 answer this FAQ: https://www.gnu.org/licenses/gpl-faq.en.html#NonvisualLegalNotices
@borkdude perhaps the pod could inspect it's args and/or babashka could have a method for asking for notice/licence files from its pods?
@borkdude it's not for oracle's benefit only, it's for the users, so they know the licence of the software they are using.
fwiw, you're unlikely to be pestered about this. Leiningen's uberjar tool violates the Apache licence by dropping all LICENSE files.