search

ohnosequences / sbt-s3-resolver

:cloud:Amazon S3-based resolver for sbt
GNU Affero General Public License v3.0
117 stars 29 forks source link

Unable to resolve dependency after migrating to sbt 1.x #61

Closed envilogger closed 6 years ago

envilogger commented 6 years ago

We encountered very strange issue when upgraded to sbt 1.2.6 Simple case: we have library utils-lang which was published to s3 with sbt 0.13.13, also we have a service which uses this lib and also uses sbt 0.13.13 and sbt-s3-resolver v0.14.0, everything worked fine until we decided to upgrade to scala 2.12 / sbt 1.2.x We upgraded to scala 2.12 successfully by releasing new version of utils-lang and service with sbt 0.13.13, but when we updated sbt to 1.2.6 in the service, and sbt-s3-resolver to v0.19.0 it failed with com.envi#utils-lang_2.12;1.0: not found. The most strange thing is that in logs I see:

[warn] ==== Releases resolver: tried
[warn]   s3://artifactory.envi.cc/releases/com.envi/utils-lang_2.12/1.0/ivys/ivy.xml
[warn]   -- artifact com.envi#utils-lang_2.12;1.0!utils-lang_2.12.jar:
[warn]   s3://artifactory.envi.cc/releases/com.envi/utils-lang_2.12/1.0/jars/utils-lang_2.12.jar

and both files (ivy.xml and utils-lang_2.12.jar) are there

Can you help me understand what is the problem here? I haven't found any info that artifacts made by sbt 0.13 and 1.3 are different and incompatible

envilogger commented 6 years ago

found the reason, it was due to wrongly setup was region all fine with the resolver :)