Fork me on GitHub
#cljdoc
<
2018-09-24
>
martinklepsch07:09:48

@justalanm thanks for stopping by 👋 I’m not on a computer right now but generally this kind of issue should only occur if - the artifact has a typo somewhere (name, version) - the artifact is in a specific repo that is not part of the default maven repositories defined by tools.deps

martinklepsch07:09:11

For debugging it might help to see if things work locally by running ./script/cljdoc ingest from the cljdoc repo as described here: https://github.com/cljdoc/cljdoc/blob/master/doc/running-cljdoc-locally.md

martinklepsch07:09:58

And if you’re lucky maybe other people around here will look into it too :)

alan07:09:07

Thanks @martinklepsch, for as much as I know the package is in Maven Centralhttps://repo.maven.apache.org/maven2/ml/dmlc/xgboost-jvm/, I can try to bump its version tonight and see what happens

alan07:09:16

I'll let you know how that goes

martinklepsch08:09:29

@justalanm also try if you can depend on it using the new deps.edn stuff

martinklepsch08:09:21

It seems that the jars for 0.72 only have the -javadoc classifier (I.e. no regular jar) and I’m not sure how tools.deps deals with that /cc @dominicm

martinklepsch08:09:15

Asked in #tools-deps as well

dominicm08:09:02

It doesn't too well. The very newest will I think I

alan08:09:37

The reason I said I'll bump the version is because I found this https://github.com/dmlc/xgboost/pull/3401 which is pretty recent and I'm guessing they're providing prebuilt jars only for 0.8

martinklepsch08:09:29

@justalanm I think the same issue will apply to 0.8 — or at least the contents of the maven repo look very similar to 0.72

alan09:09:00

Yeah I just checked and I require it like this [ml.dmlc/xgboost-jvm "0.72" :extension "pom"], the same goes for 0.8

martinklepsch10:09:16

Yeah that’s probably getting lost when constructing the class path for analysis. Will also need to check if tools deps supports the extension stuff. Feel free to create an issue for this.

zane20:09:52

I don't suppose there are plans in the works to create a cljdoc.main for use with the clojure command-line tool?

zane20:09:10

I'm imagining building cljdoc documentation locally without having to clone the repository.

zane20:09:31

If this is something that would be interest to folks I might be able to take a crack at a PR.

4