Fork me on GitHub
#cljdoc
<
2019-02-13
>
anthony-galea09:02:18

pr submitted 🙂 Just searched incanter on http://cljdoc.org and was surprised to find its docs because when I try the local ingest for incanter I also get Could not find artifact bouncycastle:bctsp-jdk14:jar:138 in central. Can it be that the modules were analysed separately? https://cljdoc.org/d/incanter/incanter-sql/1.9.3/api/incanter.sql

martinklepsch09:02:42

Each artifact is analysed separately, yes

martinklepsch09:02:00

so incanter-sql might be there while incanter itself fails for some reason

anthony-galea09:02:40

might there be differences to the local ingest then? because locally I don’t see the namespace for incanter-sql

anthony-galea09:02:52

just see the readme

anthony-galea09:02:41

actually not even the readme, i get a page with the request to build the docs

anthony-galea09:02:26

just cloned the incanter repo and ran ./script/cljdoc ingest -p incanter/incanter -v 1.9.3 --git ~/Desktop/incanter/

martinklepsch09:02:22

so incanter/incanter != incanter/incanter-sql

martinklepsch09:02:46

./script/cljdoc ingest -p incanter/incanter-sql -v 1.9.3 --git ~/Desktop/incanter/ after this you shouldn't see the request a build page anymore

anthony-galea09:02:00

i see, so the incanter modules are ingested separately

martinklepsch09:02:51

yes, they are packaged as separate jar/artifact and that's what cljdoc uses to determine boundaries

anthony-galea09:02:28

ok, i’ll submit a similar pull request on the incanter-pdf module then

martinklepsch09:02:10

There's some WIP around blurring that line a little bit, allowing namespaces from dependencies to be shown as if they are part of the artifact https://github.com/cljdoc/cljdoc/pull/264

anthony-galea09:02:46

ah good to know thanks