The main change in this is that support for s3 maven repos has been completely replaced and is now using a new impl of the Maven resolver transporter API based on the cognitect aws-api. The old version used the transporter-wagon adapter, the unmaintained spring s3 wagon, and the AWS Java SDK. Those deps have been happily dropped on the floor, and all other deps were bumped as well. Support for some newer AWS credential sources may be better, particularly when running on AWS. Also, you can explicitly set the s3 bucket region in your deps.edn like {:mvn/repos {"my-bucket-repo" {:url ""}}} - this is a feature of this transporter, not a general AWS thing.

Hmm, After update im getting a strange exception

Downloading: com/cognitect/transit-clj/0.8.319/transit-clj-0.8.319.pom from 
Error building classpath. org.apache.maven.repository.internal.DefaultModelResolver.<init>(org.eclipse.aether.RepositorySystemSession, org.eclipse.aether.RequestTrace, java.lang.String, org.eclipse.aether.impl.ArtifactResolver, org.eclipse.aether.impl.VersionRangeResolver, org.eclipse.aether.impl.RemoteRepositoryManager, java.util.List)
java.lang.NoSuchMethodException: org.apache.maven.repository.internal.DefaultModelResolver.<init>(org.eclipse.aether.RepositorySystemSession, org.eclipse.aether.RequestTrace, java.lang.String, org.eclipse.aether.impl.ArtifactResolver, org.eclipse.aether.impl.VersionRangeResolver, org.eclipse.aether.impl.RemoteRepositoryManager, java.util.List)
        at java.base/java.lang.Class.getConstructor0(Class.java:3349)
        at java.base/java.lang.Class.getConstructor(Class.java:2151)
        at clojure.tools.deps.alpha.extensions.pom$model_resolver.invokeStatic(pom.clj:49)
[...]

What are your full deps? And do they include pomegranate?

https://github.com/uxbox/uxbox/blob/docker/arm64-adaptation/backend/deps.edn

hmm not explicitly

with 1.10.1.492 works ok...

it fails always after com/cognitect/transit-clj/0.8.319/transit-clj-0.8.319.pom i dont know if is something relevant

Happy to help diagnose but you’re going to have to give me more context to repro

at this momment i don't have more context, maybe tomorrow i try to investigate more. If i found something "relevant" i ping you

thanks

ok is something related to :local/root

i commented that dependencies and the -Stree is now can resolve all deps..

the simplest reproducible case is (deps.edn):

{:deps {somepackage {:local/root "path/to/package" 
:deps/manifest :pom}}}

thx, repro'ed. I'll take a look

must be some drift in the pom model reading code across lib versions

fixed, but might be a couple days before I can release on brew (they gets antsy if you release too frequently)

should downgrade for the moment to 492

thanks! no problem i stay with 492 for the moment

new release 1.10.1.502 is now available and fixes this issue