This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-28
Channels
- # beginners (226)
- # boot (18)
- # bristol-clojurians (4)
- # cider (1)
- # clara (77)
- # cljs-dev (79)
- # cljsjs (27)
- # clojure (178)
- # clojure-austin (9)
- # clojure-dev (30)
- # clojure-gamedev (11)
- # clojure-italy (5)
- # clojure-losangeles (3)
- # clojure-poland (1)
- # clojure-spec (42)
- # clojure-uk (34)
- # clojurescript (182)
- # core-async (5)
- # core-logic (2)
- # cursive (17)
- # datascript (12)
- # datomic (33)
- # emacs (8)
- # figwheel (1)
- # fulcro (25)
- # jobs (6)
- # jobs-discuss (27)
- # lein-figwheel (1)
- # lumo (18)
- # off-topic (17)
- # onyx (5)
- # pedestal (7)
- # re-frame (30)
- # reagent (52)
- # remote-jobs (1)
- # ring (2)
- # ring-swagger (1)
- # shadow-cljs (40)
- # spacemacs (5)
- # sql (31)
- # unrepl (12)
- # vim (25)
definitely buy the bhauman TLD
so I follow the reverse dns convention for naming maven artifacts, and then name my namespace whatever I want.
@arrdem reasoning that maven group-ids have wider exposure than clojure namespaces?
@bhauman take clojure, it’s released as org.clojure/clojure
but the ns segment is just clojure.
arguably clojure is a special case in the context of clojure
I guess it does leak into java packages?
it's at least a whole language though, rather than a library
my point was that if you make a namespaced called jello
, you will be putting things into the jello
package
so you couldn't say that only clojure users notice the use the of the clojure
name
@bhauman I'd say yes to your original question of adding a group-id to rebel-readline
for sure. everyone should always use groupIds imo
I know a lot of clojure tools would have trouble with it, but I wonder if maven would allow a tag uri for a group-id
they expect it to follow the java package name rules
the other great thing about always using group-ids is, if you use lein, it gets rid of the ubiquitous *.core namespace