-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roundtrip to S3 fails with Dynamic Revisions #31
Comments
Here's an untested implementation of the proposed fix: https://github.com/acollver/ivy-s3-resolver/commit/98142489ea099e73330b75423127480615392a96 |
I have verified that my proposed fix works with both specific and dynamic versions. |
I created a pull request for this issue. Apologies for creating the issue against sbt-s3-resolver when the proposed fix belongs in ivy-s3-resolver: |
I updated my pull request to support pagination with AmazonS3.listObject |
* Added ivy dynammic revisions support (by @acollver). See [ohnosequences/sbt-s3-resolver#31](ohnosequences/sbt-s3-resolver#31)
I just released the new version with the fix: |
* Upgraded to the ivy-s3-resolver [`v0.6.0`](https://github.com/ohnosequences/ivy-s3-resolver/releases/tag/v0.6.0). See [#31](#31).
Observed Behavior
Cause
I found that the fm-sbt-s3-resolver is creating a "directory" object in S3 (an empty object that has a key ending in "/"). Creating the same "directory" object from the AWS console allows Ivy to resolve a module published to S3 using sbt-s3-resolver.
Ivy's FileRepository returns a mix of directory and file names (but one level deep unlike the S3 listObjects overload that is currently used): https://github.com/sbt/ivy/blob/2.3.x-sbt/src/java/org/apache/ivy/plugins/repository/file/FileRepository.java#L99-L112
Proposed Fix
Update https://github.com/ohnosequences/ivy-s3-resolver/blob/master/src/main/java/ohnosequences/ivy/S3Repository.java#L114-L133
The text was updated successfully, but these errors were encountered: