Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 29 19:15
    pjfanning commented #58
  • Jan 29 17:50
    franchev commented #58
  • Jan 23 22:22
    geraldstanje commented #63
  • Jan 23 15:37
    geraldstanje commented #63
  • Jan 23 15:35
    geraldstanje commented #63
  • Jan 23 15:08
    montpetitg commented #63
  • Jan 23 15:07
    montpetitg commented #63
  • Jan 23 05:22
    geraldstanje commented #63
  • Jan 23 05:22
    geraldstanje commented #63
  • Jan 23 05:21
    geraldstanje commented #63
  • Jan 17 18:57
    montpetitg commented #63
  • Jan 17 18:56
    montpetitg commented #63
  • Jan 02 14:25
    wiktorolko commented #63
  • Dec 21 2019 14:41
    maziyarpanahi commented #63
  • Nov 20 2019 22:05
    tpiron commented #63
  • Nov 19 2019 17:07
    jjmalina opened #63
  • Sep 06 2019 02:35
    kimxogus opened #62
  • May 13 2019 11:38
    schneist commented #58
  • May 13 2019 11:19
    schneist commented #58
  • May 13 2019 11:19
    schneist commented #58
Michael Ahlers
@michaelahlers
:clap:
Alexey Alekhin
@laughedelic
@/all New release: v0.19.0 with a nice contribution from @tsuyoshizawa :tada:
Fernando
@nandotorterolo
Hi, icould you provide me and example for, 'sbt.version=0.13.15' and 'scalaVersion := "2.12.3"', is this line in plugins.sbt ok? resolvers += Resolver.jcenterRepo
addSbtPlugin("ohnosequences" % "sbt-s3-resolver" % "0.16.0")
Alexey Alekhin
@laughedelic
Hi @nandotorterolo. If you are using sbt-0.13, the right version of the sbt-s3-resolver is 0.16.0, this is correct. But you have to check the readme for that version: it was published to a different repository:
resolvers += "Era7 maven releases" at "https://s3-eu-west-1.amazonaws.com/releases.era7.com"
addSbtPlugin("ohnosequences" % "sbt-s3-resolver" % "0.16.0")
Regarding, scalaVersion := "2.12.3", I guess, you have it in your build.sbt, which is irrelevant for the plugin. Scala version which is used for the plugins is determined by the version of sbt:
  • sbt 0.13 works with Scala 2.10
  • sbt 1.0 works with Scala 2.12
Do you have any good reason to stay on sbt 0.13 instead of upgrading to sbt 1.0?
Fernando
@nandotorterolo
thanks for your detailed explanation, reason is that I need other plugins with status wip: https://github.com/sbt/sbt/wiki/sbt-1.x-plugin-migration
Alexey Alekhin
@laughedelic
OK. I'm just curious what are they? (if not too many)
By the way, you should be aware, that this list is updated mostly manually, so some things are out of date there.
Fernando
@nandotorterolo
good tip, maybe I need to upgrade sbt version, and upgrade all plugins, I will post information if I can not resolve them
Alexey Alekhin
@laughedelic
:+1:
Fernando
@nandotorterolo
@laughedelic let me explain my use case, I actually use 'io.get-coursier:sbt-coursier' plugin, which It doesn't currently work with the SBT 1.0. If I do not use coursier plugin, sbt-s3-resolver works!, but if I use both, it doesn't, and have this message '[warn] Unrecognized repository <name> resolver, ignoring it' It was reported time ago, will reopen the bug. coursier/coursier#182
Fernando
@nandotorterolo
Alexey Alekhin
@laughedelic
I don't know anything about this issue, will have to read that threah later.
Have you tried using https://github.com/rtfpessoa/coursier-s3 instead?
Fernando
@nandotorterolo
yes, but without success, unmaintained repo :( rtfpessoa/coursier-s3#4
Alexey Alekhin
@laughedelic
@nandotorterolo OK, I see. It's sad that it was abandoned.. I'm not sure I can help you right away with coursier as I don't use it myself and I don't know when I will have time to try it out and dig into this issue. Try asking coursier people and if you figure it out or get any relevant information, please keep me updated, write here or open an issue. It will be much appreciated by me and other user who might have similar problems.
Fernando
@nandotorterolo
ok, will post in coursier-team and try to move this stuff, thanks!
Alexey Alekhin
@laughedelic
ánimo! :+1:
Artsiom Miklushou
@mikla

Hello there.
I'm facing problems with resolving dependencies from S3.

I have ~/.aws/config like this:

[default]
region = eu-central-1
output = json

[my-project]
region = eu-central-1

I have ~./aws/credentials like this

[my-project]
aws_access_key_id = A...
aws_secret_access_key = X...

(I also tried to add empty [default] section here.

aws s3 ls s3://releases.my-project.io/some-ivy-file.ivy --profile my-project returns me list of files.

But, sbt can't resolve deps.
version 0.13.16

I also tried to export AWS_PROFILE=my-project without any luck.

Any suggestions? Thanks in advance

Artsiom Miklushou
@mikla
MacOs 10.13.1
Michael Ahlers
@michaelahlers
@mikla, for troubleshooting purposes (I understand this is not optimal), what if you try adding the following to any SBT file?
awsProfile := "my-project"
s3region := com.amazonaws.regions.Regions.EU_CENTRAL_1
Alexey Alekhin
@laughedelic
Oh, sorry @mikla, I forgot to reply to you! :sweat:
@michaelahlers thanks for support :+1:
Michael Ahlers
@michaelahlers
Glad to help, @laughedelic! I've brought S3 Resolver into projects at work, so I'm current on tutoring others a bit. ;)
Alexey Alekhin
@laughedelic
Cool! :clap:
@mikla if you're using sbt 0.13 you can only use some old version of the plugin, I think 0.16.0. right?
So in that old version awsProfile setting affected only credentials, not the region (hence, as @michaelahlers says, you have to set the region explicitly). In the newer versions it has been fixed, but it's available only for sbt-1.x
Artsiom Miklushou
@mikla

@michaelahlers Same error

@laughedelic right, I'm using 0.16.0.

Artsiom Miklushou
@mikla
It shows me correct awsProfile and credentials via sbt awsProfile & showS3Credentials tasks
I see in the [debug] section that it tried to download needed dependency but failed.
But it's possible to download it with aws s3 cp
Alexey Alekhin
@laughedelic
@mikla Please, post that debug/error output and any setting you have related to this plugin. Also your general setup: is it a multi-project build?
Pablo
@pablottz_twitter
Hi I´m new to this plugin, please for give my ignorance, I want to use S3 as a dependence repo, is it required for me to use a library like this one, or there is a work around for using the sbt 'publishTo' pointing to my S3 bucket URL, without using any third party code like this one? Thanks
Alexey Alekhin
@laughedelic
@pablottz_twitter hi! If you want to publish your library to S3, you cannot do it without any third-party plugin. So yes, you can use sbt-s3-resolver for that. And if you want (only) to resolve dependencies from S3, it depends: you can resolve public maven artifacts.
Pablo
@pablottz_twitter

Thank you very much @laughedelic , I understand now and I will use this plugin, but for more information detail, I would like to know why is this, maybe it is because SBT expects a dependency server configured as a dependency management like artifactory, and S3 it's obviusly not configured as a dependency management out of the box?

Thanks in advance

Pablo
@pablottz_twitter
btw my project is not resolving the plugin since it's trying to find the path https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/ohnosequences/sbt-s3-resolver/scala_2.10/sbt_0.13/v0.19.0/ivys/ivy.xml, but unfortunatelly there is no path for scala_2.10, only for scala_2.12, is there a way to make SBT to point to scala_2.12 instead. I'm using this in my project val scalaVersions = Seq("2.11.12", "2.12.5")
Alexey Alekhin
@laughedelic
@pablottz_twitter the latest version of this plugin is published only for sbt 1 (which uses Scala 2.12). So you either need to update your sbt version (in project/build.properties) or use an older version of this plugin (not recommended). See the installation docs.
Also, I'm not sure what was your question before that. sbt works with different kinds of artifact repositories using different resolvers. There is no S3 resolver for sbt out of the box and this is exactly why this plugin exists. It uses an implementation of an ivy resolver for S3: https://github.com/ohnosequences/ivy-s3-resolver.
Michael Ahlers
@michaelahlers

@pablottz_twitter, please excuse the delay. Just saw your PM a moment ago:

I´m trying to use sbt-s3-resolver, can you tell m e how to resolve the import com.amazonaws.services.s3.model.Region please?

Are you still having trouble with the AWS imports?

Pablo
@pablottz_twitter
Hi Michael, actually I'm still having issues :s
Alexey Alekhin
@laughedelic
@pablottz_twitter don't hesitate to ask if you still need help
Michael Ahlers
@michaelahlers
Is there any kind of sbt-s3-resolver integration with Coursier? (Searching, but not turning up anything viable.)
Alexey Alekhin
@laughedelic
@michaelahlers Not that I know of. Coursier mentions some project, but AFAIK it's abandoned.
Fernando
@nandotorterolo
@michaelahlers you could use https://github.com/frugalmechanic/fm-sbt-s3-resolver, I am using : addSbtPlugin("com.frugalmechanic" % "fm-sbt-s3-resolver" % "0.12.0") . and addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-RC11")
damienbailly
@damienbailly
Hello, it looks like the older versions of sbt-s3-resolver (for sbt 0.13) are no longer accessible with this resolver "Era7 maven releases" at "http://releases.era7.com.s3.amazonaws.com". Can someone take a look? (It'd be nice to publish them to jcenter as well)
geraldstanje
@geraldstanje
@laughedelic hi you please re-add sbt-s3-resolver;0.14.0? currently we get: ohnosequences#sbt-s3-resolver;0.14.0: not found
Tristan Piron
@tpiron
Hey, there is an issue open (#63) concerning sbt-s3-resolver not being available anymore ( ohnosequences:sbt-s3-resolver:0.14.0 (scalaVersion=2.10, sbtVersion=0.13) )
is someone working on re-publishing it ?
it happened a few months ago but got re-added after a few days, and looks like the issue happened again on Jan17th and is still ongoing
Alexey Alekhin
@laughedelic
@/all Sorry for the long absence, I didn't use Gitter in a long time. Unfortunately, I can't help with this project anymore. I left the company that owns that repository ~2 years ago and I don't have access to the Github repository or Bintray since then.
In any case, I think the project at this point is not maintained and I wouldn't recommend using it anymore. If I was still using it myself, I'd probably fork and keep maintaining it, but that's not the case.
There is a very similar plugin with the same functionality that seems much more up to date: https://github.com/frugalmechanic/fm-sbt-s3-resolver. I can't recommend it because I haven't used it myself, but it's definitely worth a try.