Releases: ohnosequences/sbt-s3-resolver
Releases · ohnosequences/sbt-s3-resolver
sbt-s3-resolver v0.11.0
- Started using nice-sbt-settings plugin (which means, that we don't crosscompile anymore, only scala-2.10/sbt-0.13);
- Updated to ivy-s3-resolver 0.5.0;
sbt-s3-resolver v0.10.1
Bugfix: made parameters of the S3Resolver constructor it's fields
sbt-s3-resolver v0.10.0
- Changed type of
s3credentials
key toAWSCredentialsProvider
from the AWS Java SDK. See #20, #21 and the updated Readme section about using credentials.
sbt-s3-resolver v0.9.0
- Entirely changed the way of resolver construction. See Readme.
- Added settings for region and overwrite.
s3credentialsFile
ands3credetials
don't useOption
anymore: you either load them or not use at all.
sbt-s3-resolver v0.8.0
- Changed
s3credentialsFile
type toOption[File]
instead ofOption[String]
; - It is set by default to
~/.sbt/.s3credentials
; - Minor improvements to handling situations with no existing credentials file, etc.
sbt-s3-resolver v0.7.0
- #11: IvyResolver is now M2 compatible (thanks to @aniketbhatnagar)
- #13: Upgraded to ivy-sbt-resolver
v0.3.0
:- adds parameter for setting region (default is Ireland);
- adds option for allowing artifacts overwriting (default is
false
);
- #14: the code now is in
ohnosequences.sbt
package namespace. It doesn't affect usage of plugin, except of using it as a library dependency;
sbt-s3-resolver with cross-building
- this version is cross-built and cross-published for sbt
v0.12
(scala-2.9.2) and sbtv0.13
(scala2.10.2
). - there is one change in usage: now
s3credentials
ands3credentialsFile
settings should be set withoutin Global
scope (see readme). - and now the plugin is published maven-style.
Region bugfix
This release resolves issue #8. Also it suggests another way of setting credentials in Readme.
S3Resolver as a type
We can't extend sbt Resolver
, but we needed a self-sufficient type (for proper serialization of it's values), so here it is!
So changes are
- instead of
s3resolver
function, there is nowS3Resolver(name: String, url: String, patterns: Patterns = Resolver.defaultPatterns)
constructor - it has a method to convert to sbt
Resolver
type:toSbtResolver(credentials: S3Credentials): Resolver
- patterns in costructor are
Patterns
not just a string with one pattern, because we want generality for ivy- and maven-style publishing (resolving for maven so far doesn't work).
Migrated to ivy-s3-resolver
In this version we migrated from weird spring-aws-ivy
to @evdokim's brand new ivy-s3-resolver
, and got rid of strange dependencies!
Usage changes:
- no more
pattern
ands3resolver
setting keys - for creating a resolver use
s3resolver
function - it requires credentials and returns Resolver (without Option)
For more details see Readme.