not sure it's important, but I was reminded of a small caching problem I had with tools-deps: it seems to cache the classpath per list of aliases enabled or something similar that excludes the java version, while maven allows selecting different dependencies based on java version right inside the pom

so the same deps.edn might produce different classpaths based on JDK used

a repro would be helpful. By design tools.deps doesn't attempt to mimic Maven

https://github.com/cljfx/cljfx/ is a repro

that is not a repro, that's a repo

good point

"`clojure -A:foo -Spath` -> expected this, but received that" is a repro

ah, sorry, I'll make a repro

repro

"switch java version to 8 so it should trigger different profile according to activation rules" is not something clj does

that's a maven thing

you can make Clojure aliases that include the desired classifier variant of cljfx if you like

but it's what it does?

it's what Maven does

clj is not Maven and I have no plans to add that

sure, I understand that is abusing maven features

it's very much using Maven features as they were intended

just don't expect clj to support all of that (this is just the tip of the iceberg)

Okay, thanks

I have deps that specifies a private github repo via SSH (e.g git@github...) This works finally locally. But i'm trying to know run my build scripts as part of a deployment pipline (specifically google steps). I'm running into some complications concerning deployment keys, ssh, etc... by any chance has anyone been through this before and have any advice?

It may be easier to use the git build step to fetcch the repo and then treat it as a local dep

Or the docs for private git repos might help directly https://cloud.google.com/cloud-build/docs/access-private-github-repos

There's no actual fix mentioned in https://ask.clojure.org/index.php/8725/deps-support-newer-private-file-formats-types-such-ed25519. Anyone know what the fix is? We're onboarding new developers and they all hit this issue. Guessing the fix has something to do with generating an older ssh key?