I have previously been using WSL which works fine for me, but I'm scripting out running local environments for our testers and they all run windows and I'd rather not have to have them all install WSL

Windows historically has had an issue with java classpath lengths being too long. I have no idea if fixing this will allow you to run the transactor on windows, but it may not be a datomic specific issue, rather a windows+java issue.

ah rats that means I'm going to probably have to go about this the harder way.

One trick for getting around this is to write the classpath into a jar manifest then run the jar with java -jar

(the “runner” jar has nothing in it but a manifest with a classpath)

is there an upper limit on the java version for a transactor?

Because another solution as I understand could be to build a classpath file instead of the CP_LIST

there are some speculative generic fixes for this for clj on windows

not sure if that applies here

maybe you're not using clj so it doesn't matter

what I'm trying to do is run bin/transactor.cmd in a script to start a transactor

I was told by Marshall I think (although I saw nothing official) that java11 is supported

I think I'm just going to go down the path of windows users are going to have to have wsl.

your “classpath file” can be the jar with manifest.

actually yeah, you're right, I like that much better.

Thanks for all the help

build CP_LIST with spaces instead of colons, write to a file, like Class-Path: CP_LIST then jar cfm cplist.jar Manifest.txt

actually you can just distribute the jar by itself, since that classpath isn’t going to change