Clojurians Log v2

I’ve just run into the classpath too long issue (TDEPS-120). I’ve tried the “reduce the path to your local Maven repository” advice without any luck (my classpath is still too long even with a path to the maven repo of /mvn. Is there anything else I can try, or am I out of luck until TDEPS-120 is fixed? (I’m on 1.10.3.822). Thanks!

@paulbutcher A workaround is to create an uberjar from your deps and put that uberjar on your classpath. It's an ugly workaround, but therefore it's called a workaround.

That does sound ugly :rolling_on_the_floor_laughing:. Is there a cheatsheet explaining how to go about doing that lying around?

for creating an uberjar I would use seancorfield/depstar

then you can add the uberjar to your classpath like:

{:deps
 {db/driver {:local/root "/path/to/db/driver.jar"}}}

I’m using that already to create the uberjar for my project: I may be missing something, but how do I get depstar to create the uberjar without running into exactly this issue?

I may revert back to doing what I was doing before, which is develop on my Mac and play with port forwarding to get the Windows machine I need to test on (I have a Windows-specific bug I’m trying to nail) to connect through to the code running on the Mac…

that's a good question: creating the uberjar itself also runs into this issue? I've gotten away with this before where the uberjar worked, but not the normal approach

Yeah, I have a single deps.edn which describes a combined clojurescript front-end and clojure back-end so there are a lot of dependencies.

make multiple uberjars? ;)

we have split our big app up into front-end and back-end deps

under two different aliases

I could break them apart, but given that I’m not looking to develop on Windows as a matter of course, it might be easiest to give up on getting it to build there and just play port-forwarding games.

you could build the uberjar on your mac and then use that on Windows

or use WSL to create the uberjar

Yeah, but what I really want to do is run the development build so that I can watch what’s going on. I have a bug which only manifests on Windows Chrome (Mac Chrome runs fine). So what I hoped to do was run it with Figwheel and all that other goodness on Windows.

beware of AOT though: don't AOT your own sources when you want to develop

I think I’ll just give up and get port forwarding sorted.

oh then you can solve it actually easier. run your development in WSL and then use the Windows browser to view your WSL dev server

Ah! Of course.

Thanks - I should have worked that out