This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-11
Channels
- # adventofcode (116)
- # aleph (10)
- # announcements (2)
- # beginners (67)
- # boot (3)
- # calva (17)
- # cider (8)
- # cljdoc (27)
- # cljsrn (6)
- # clojure (144)
- # clojure-austin (3)
- # clojure-boston (1)
- # clojure-dev (25)
- # clojure-europe (4)
- # clojure-italy (26)
- # clojure-losangeles (4)
- # clojure-nl (28)
- # clojure-russia (1)
- # clojure-uk (34)
- # clojurescript (130)
- # cursive (20)
- # datomic (69)
- # emacs (14)
- # figwheel-main (2)
- # fulcro (31)
- # graphql (3)
- # hyperfiddle (3)
- # jobs (1)
- # jobs-discuss (1)
- # kaocha (1)
- # leiningen (2)
- # lumo (2)
- # nrepl (1)
- # off-topic (182)
- # onyx (5)
- # re-frame (88)
- # reagent (12)
- # reitit (2)
- # ring-swagger (13)
- # shadow-cljs (136)
- # tools-deps (28)
- # vim (4)
Hello! Am I correct that the only bits cljdoc reads out of the <scm>
tag in a pom.xml are the url
and tag
fields? It look like it to me from the source, just wanted to double-check
@timgilbert that sounds correct to me 😄
Sweet, thanks
It does fall back the global <url>
tag if there's no <scm>
tag
Mind sharing why you're asking? 🙂
I’m working on a little utility to post-process the results of clojure -Spom
and rewrite the version, groupId
and artifactId
Since I’m in there anyways I figured I might as well try to put in the stuff cljdoc uses
ohh, that sounds useful — for packaging deps.edn based projects into jars and stuff?
One thing I wasn’t sure about was whether there was some special sauce I needed to get the “view source” links to work correctly
Yeah, precisely
We've been meaning to also package cljdoc as a jar just so we can put it on cljdoc as well 🙂
Hah, nice
for view source links to work you need either a) a <tag>
in the scm portion or b) a tag with the version string like 1.0.0
or v1.0.0
You can partly do it right now by creating a pom.xml and using juxt/pack to make a skinny jar, but the deployment bit is not there yet
yeah, also I really don't like the way you have to post-process the clj -Spom pom.xml
there's a deps-deploy
project though (linked in the issue above)
Same, and I don’t like checking in partially-generated stuff into source control, package.lock be damned
Oh right! I knew I’d seen one somewhere
Perhaps it would be helpful to "borrow" from boot's pom.xml generation stuff
(linked in the deps-deploy issue)
Yeah, I looked at that. The actual code to update is pretty short, though, and I’m able to just invoke the clojure -Spom from tools.deps so it doesn’t need a separate JVM invocation
I see, I guess staying to the -Spom output as much as possible makes sense, thus updating might be the better approach
Yeah, I’m going to go with it as a first approach. I have it working now, just need to see if I can get the full path to clojars to work
That would be awesome — please share your results in https://github.com/cljdoc/cljdoc/issues/206 if you don't mind 🙂