Clojurians Log v2

I get javadoc as well when using this "syntax":

java.util.UUID/.version

This is for sure interesting, as this is now valid Clojure syntax. So I could write my "production" code as:

(let [my-uuid (java.util.UUID/randomUUID)]
  (java.util.UUID/.version my-uuid))

(let [my-uuid (java.util.UUID/randomUUID)]
  (.version my-uuid))

Thanks for investigating this! 🙏 There’s a command for enabling nrepl message logging. Maybe you see something there that can shed some light?

Maybe the javadoc work sin more situations as I thought:

(let [my-env ^OrtEnvironment (OrtEnvironment/getEnvironment)]
    (.getVersion my-env)
    (.isTrainingEnabled my-env))

so I think "it should work" under tow conditsion: 1. type hints are added 2. I made sure (somehow) that the "source jars" are present in my local maven repo. The simplest way for downloading them it to run:

clojure -X:deps mvn-pom && mvn dependency:sources

If I write the same like this, it javadocs and completion work without type hints: (but we still need the "sources jars" downloaded)

(let [my-env-1 (OrtEnvironment/getEnvironment)]
    (OrtEnvironment/.getVersion my-env-1)
    (OrtEnvironment/.isTrainingEnabled my-env-1))

And here the new "clojure.java.doc" libray could step in, as it allows dynamic download of the javadoc jars (which are enough to render "javadoc"). nrepl (and therefore Calva) uses so far the "sources jars" it seems.

Yes, I saw that Calva gets all javadoc info from nrepl. so maybe we should only document somewhere, this "tips" to make it work in more situations 0. java class is imported 1. type hints are added 2. I made sure (somehow) that the "source jars" are present in my local maven repo. or use "new syntax", and then 2. is not needed any more. but '0' and '2', are still required)

(OrtEnvironment/.isTrainingEnabled my-env-1)

I suggested this documentation as well here: https://github.com/BetterThanTomorrow/calva/issues/2965 The "custom snippet" I put there is the basically an "alternative" way of getting javadoc without the need of 2) But ideally nrepl will integrate the "clojure.java.doc" library one day, so that download of "source jars" is not needed at all anymore for Calva users even when using "calva build in javadoc" But until then, docu of existing javadoc support + example snippet somehwere is probably the way forward

@seancorfield was active in the same area, I just saw: https://ask.clojure.org/index.php/14715/improve-javadoc-especially-for-tool-usage

This is interesting as well: Cider automates partially the "source jars download". "CIDER", not nrepl... So Calva does not get it "for free". https://docs.cider.mx/cider/usage/working_with_documentation.html#obtaining-source-jars

We should follow CIDER’s example there.

yes, probbaly.

I would start by documenting this: 'clojure -X:deps mvn-pom && mvn dependency:sources' Not too bad, but "mvn" required, restart of repl needed, and to be repeated when deps.edn changes.

Doing this and "type hinting" improves the javadoc support considerably, without any work in Calva.

Updates to the docs are welcome!

ok, I give it a go.

https://github.com/BetterThanTomorrow/calva/pull/2967

Awesome. I merged it. Should be updated in a few moments.