cljdoc

https://cljdoc.org/ & https://github.com/cljdoc/cljdoc
timgilbert 2018-12-11T14:26:22.028Z

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

martinklepsch 2018-12-11T14:44:23.028500Z

@timgilbert that sounds correct to me 😄

timgilbert 2018-12-11T14:44:50.029Z

Sweet, thanks

martinklepsch 2018-12-11T14:45:20.029600Z

It does fall back the global <url> tag if there's no <scm> tag

martinklepsch 2018-12-11T14:45:40.030200Z

Mind sharing why you're asking? 🙂

timgilbert 2018-12-11T14:46:33.031100Z

I’m working on a little utility to post-process the results of clojure -Spom and rewrite the version, groupId and artifactId

timgilbert 2018-12-11T14:47:08.031900Z

Since I’m in there anyways I figured I might as well try to put in the stuff cljdoc uses

martinklepsch 2018-12-11T14:47:30.032400Z

ohh, that sounds useful — for packaging deps.edn based projects into jars and stuff?

timgilbert 2018-12-11T14:48:01.033200Z

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

timgilbert 2018-12-11T14:48:02.033400Z

Yeah, precisely

martinklepsch 2018-12-11T14:48:39.034100Z

We've been meaning to also package cljdoc as a jar just so we can put it on cljdoc as well 🙂

timgilbert 2018-12-11T14:48:51.034500Z

Hah, nice

martinklepsch 2018-12-11T14:48:59.035Z

https://github.com/cljdoc/cljdoc/issues/206 cc @ichigo

martinklepsch 2018-12-11T14:49:54.037Z

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

timgilbert 2018-12-11T14:50:04.037400Z

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

martinklepsch 2018-12-11T14:50:36.038100Z

yeah, also I really don't like the way you have to post-process the clj -Spom pom.xml

martinklepsch 2018-12-11T14:51:09.039100Z

there's a deps-deploy project though (linked in the issue above)

timgilbert 2018-12-11T14:51:46.039600Z

Same, and I don’t like checking in partially-generated stuff into source control, package.lock be damned

martinklepsch 2018-12-11T14:51:58.040Z

https://github.com/slipset/deps-deploy/issues/7

timgilbert 2018-12-11T14:52:10.040500Z

Oh right! I knew I’d seen one somewhere

martinklepsch 2018-12-11T14:52:21.040800Z

Perhaps it would be helpful to "borrow" from boot's pom.xml generation stuff

dominicm 2018-12-12T08:36:44.045600Z

This is how pack started!

martinklepsch 2018-12-11T14:52:35.041400Z

(linked in the deps-deploy issue)

timgilbert 2018-12-11T14:53:22.042300Z

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

martinklepsch 2018-12-11T14:54:50.043600Z

I see, I guess staying to the -Spom output as much as possible makes sense, thus updating might be the better approach

timgilbert 2018-12-11T14:56:13.044800Z

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

martinklepsch 2018-12-11T14:58:54.045400Z

That would be awesome — please share your results in https://github.com/cljdoc/cljdoc/issues/206 if you don't mind 🙂

👍 1