This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-25
Channels
- # beginners (26)
- # boot (1)
- # cider (21)
- # cljdoc (26)
- # cljs-dev (7)
- # clojure (99)
- # clojure-gamedev (6)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-spec (5)
- # clojure-uk (59)
- # clojurescript (49)
- # clojutre (6)
- # component (13)
- # core-async (2)
- # cursive (30)
- # data-science (2)
- # datomic (29)
- # emacs (9)
- # fulcro (100)
- # hyperfiddle (1)
- # jobs (2)
- # luminus (4)
- # lumo (23)
- # off-topic (22)
- # other-languages (37)
- # parinfer (1)
- # re-frame (2)
- # reagent (5)
- # reitit (12)
- # ring (12)
- # rum (3)
- # shadow-cljs (168)
- # slack-help (1)
- # spacemacs (7)
- # specter (2)
- # tools-deps (8)
- # vim (11)
- # yada (3)
@martinklepsch Have the instructions for local building involving muuntaja been tested recently? I just tried them with no luck (deets next). Simply sanity checking muuntaja with lein test
resulted in
Caused by: java.io.FileNotFoundException: Could not locate jsonista/core__init.class or jsonista/core.clj on classpath.
The ingest itself failed on
Error building classpath. Could not find artifact muuntaja:muuntaja:jar:0.6.0-alpha1 in central ( )
org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact muuntaja:muuntaja:jar:0.6.0-alpha1 in central ( )
btw, the --git
path is supposed to be where I cloned muuntaja, yes?
@hiskennyness instructions were buggy pushed an updated version
https://github.com/cljdoc/cljdoc/commit/8c56acab66a75db8c1faa6a981c30a4c80ad6bb2
@martinklepsch the update on ClojureVerse was a good idea :thumbsup: I’m really looking forward to support for Dash docsets
Exception in thread "main" clojure.lang.ExceptionInfo: Could not analyze muuntaja.core {}
Caused by: java.io.FileNotFoundException: Could not locate jsonista/core__init.class or jsonista/core.clj on classpath., compiling:(muuntaja/format/json.clj:1:1)
So that is progress, the error is now the same as simply running lein test
in the muuntaja directory.
Hang on, more wi-fi issues. Might be a factor.
I don‘t know about muuntaja’s tests and would consider it unrelated to cljdoc. Maybe @ikitommi can weigh in some time tomorrow.
I think the cljdoc instructions should work now :)
@martinklepsch Sorry if I was unclear. The cljdoc example of a local build of muuntaja fails. I ran lein test
as a sanity check. That fails, now with the same error as the doc build. So methinks we just need a more reliable example target? But I agree with your overall conclusion and will return to trying the local build on my own project. I was doing the muuntaja build only because mine had failed on the issue you have now corrected.
Aint software — and documentation! — fun? 🙂
OK, still no luck. Maybe if I post what I am doing here I will see it myself. 🙂 Here is the maven from my Clojars page:
<dependency>
<groupId>com.tiltontec</groupId>
<artifactId>matrix</artifactId>
<version>0.1.5-SNAPSHOT</version>
</dependency>
I have run lein install
in the matrix repo.
That says
Created /Users/kennethtilton/matrix/cljs/matrix/target/matrix-0.1.5-SNAPSHOT.jar
Wrote /Users/kennethtilton/matrix/cljs/matrix/pom.xml
“target” in there looks like exploring.
But looking at pom.xml I do not see “target”, so I wager that is in my repo but not in maven.
pom.xml:
<?xml version="1.0" encoding="UTF-8"?><project xmlns="" xmlns:xsi="" xsi:schemaLocation="
<modelVersion>4.0.0</modelVersion>
<groupId>com.tiltontec</groupId>
<artifactId>matrix</artifactId>
<packaging>jar</packaging>
<version>0.1.5-SNAPSHOT</version>
<name>matrix</name>
<description>Matrix dataflow library for CLJS</description>
<url>http://tiltontec.com</url>
....etc
This command
./script/cljdoc ingest -p com.tiltontec/matrix \
-v 0.1.5-SNAPSHOT \
--jar ~/.m2/repository/com.tiltontec/matrix/0.1.5-SNAPSHOT/matrix-0.1.5-SNAPSHOT.jar \
--pom ~/.m2/repository/com.tiltontec/matrix/0.1.5-SNAPSHOT/matrix-0.1.5-SNAPSHOT.pom \
--git ~/matrix/cljs/matrix \
--rev "master"
OK, those com.tiltontec
s get expressed in maven as com/tiltontec/… testing that.
OK, I got it to build! Switching to com/tiltontec
gave me a bunch of errors so I dropped the com.
prefix altogether and it ran OK, with interesting exception that I am again getting the SCM complaint. I have not pushed the drop of the com to Github so will try that. Progress!
The doc might want to emphasize where group, artifact and version go — I thought metosin
was a Maven thing! And unless the flexibility is needed, how about having the script take the those as options and generate the rest of the command? Jes thinkin out loud, but for Java/Maven dummies like me it might save you some FAQs.
Finally, I see other projects follow the “com.<website>” convention so advice on how I could have gotten it to work would be welcome.