@alexmiller While that may be happening, the S3 Maven dep approach would result in a classnotfound exception when loading dev-local in the REPL (something with fressian). Switching to local/root with the jar does not result in the classnotfound. I also uploaded a pom to S3 and that approach did not result in a classnotfound.
what jar are you talking about wrt s3?
dev-local?
if so, what you're saying makes sense
afaik, maven will use the pom to report deps (which is a layer that clj is going through for that)
Yes - dev-local.
To be clear, here's what works and doesn't work. S3 jar - classnotfound S3 jar, jar md5 - classnotfound S3 jar, jar md5, pom - works local/root jar - works
yeah, that makes sense to me. sorry I didn't understand what you were doing earlier
local/root jar will use the pom inside the jar