Thanks for asking @U050SC7SV. No, not yet. Production does API analysis currently only on jdk17. That's an interesting note on jdk19. I guess folks would typically want to use the --enable-preview java opt for jdk19?

likely yes, if you're using j19 it's probably to test the new features (like loom)

At work, we've talked about adding --enable-preview to all our JDK invocations so that we can leverage preview fixtures in any JDK we use, so that might be worth considering regardless of the JDK used for running the analysis. At least you'd be future-proofed for any JDK upgrades that cljdoc gets 🙂

Thanks, https://github.com/cljdoc/cljdoc/issues/275#issuecomment-1332532432.

Nope, you didn't miss it, only jdk17 currently.

that should do it: https://github.com/cljdoc/builder/pull/6

Sorry @U050SC7SV https://github.com/cljdoc/builder/pull/6#issuecomment-1332503852. If only it were so easy!

Yeah I suspected that :/

I missed that issue on gh, interesting discussion

@UE21H2HHD What analysis would break switching from JDK17 to JDK19? (I hoped that link would give specifics -- or do I need to dig deeper into those linked issues in that comment?)

Ah, the Thread/sleep issue? Yes, we ran into that updating to JDK19, but that was a while back and I'd forgotten.

Ya @U04V70XH6, that's the culprit I know about.

That issue is so old and long. Here's the https://github.com/cljdoc/cljdoc/issues/275#issuecomment-1326642637 on JDK19 Thread/sleep