Dynamodb-local dependency failure again.
See original GitHub issueThis follows the same issue as the pre-February (2017) failures when the repo was changed to HTTPS. Cannot build the examples currently:
Could not resolve dependencies for project com.amazonaws:aws-dynamodb-examples:jar:1.0.0: Failed to collect dependencies at com.amazonaws:DynamoDBLocal:jar:[1.11.89,2.0.0)
Have the current repo setting in my pom:
<repository> <id>dynamodblocal</id> <name>AWS DynamoDB Local Release Repository</name> <url>https://s3-us-west-2.amazonaws.com/dynamodb-local/release</url> </repository>
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6
Top Results From Across the Web
AWS DynamoDbLocal v.1.19.0 is broken
It seems Amazon released a new version for DynamoDbLocal today (10/08/2022) with an empty jar file into thir specific repository.
Read more >AWS DynamoDbLocal v.1.19.0 is broken - Stack Overflow
It seems Amazon released a new version for DynamoDbLocal today (10/08/2022) with an empty jar file into thir specific repository.
Read more >added DynamoDB Local Release Repository — Bitbucket
Hi guys! You have ERROR: Could not resolve dependencies for project com.atlassian.connect:atlassian-connect-spring-boot-sample-dynamodb: ...
Read more >Error handling with DynamoDB - AWS Documentation
Discover the best practices for handling client and server errors and exceptions returned by Amazon DynamoDB operations.
Read more >How to use AWS Dynamo DB Local - YouTube
In this video I will show you how to install and start Dynamo DB Local using direct local install and Docker Image.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I ended up resolving this a while back so I don’t really remember the specifics, but I think it was due to some aggressive Maven repository settings in your settings.xml (~/.m2/settings.xml). Just temporarily remove the settings file (it’s not required) and then try building again. Once it’s downloaded into your local then you can put your settings.xml file back.
Cool!
On Friday, May 4, 2018, temadison notifications@github.com wrote: