This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-17
Channels
- # announcements (1)
- # aws (7)
- # babashka (5)
- # calva (56)
- # cider (13)
- # clj-commons (1)
- # clj-kondo (12)
- # clj-yaml (35)
- # clojure (84)
- # clojure-europe (93)
- # clojure-sg (2)
- # clojure-uk (1)
- # clojurescript (10)
- # conjure (37)
- # core-typed (1)
- # cursive (31)
- # duct (1)
- # figwheel-main (4)
- # fulcro (2)
- # holy-lambda (2)
- # humbleui (3)
- # membrane (118)
- # off-topic (46)
- # pathom (8)
- # podcasts-discuss (5)
- # releases (2)
- # rewrite-clj (13)
- # sci (27)
- # shadow-cljs (17)
- # tools-deps (12)
Hi folks: I'd like to roll an OSS library as a jar, and I'm wondering if you need to include the license in the jar file, and if so, does it matter where it goes?
seems like a good idea
I think it is common to include at the root but there is no explicit place anything looks at
https://docs.oracle.com/javase/tutorial/deployment/jar/manifestindex.html Is there a way to document the license and its path using the jar's Manifest file?
the most common way to specify a license is with a Maven pom, which has some attributes for this
It seems that lein adds both a copy of the license from the project root into the META-INF
folder of the jar, but also adds a license xml section into the pom.xml
. Am I correct that tools.build
does not provide any such feature?
it does the same
or rather it makes a pom, and can sync from a template pom.xml if you provide one, which can include license info