amazon-dynamodb-lock-client 1.2.0 is not in maven central?

Seems like 1.2.0 is not in maven central

Feb 23 '19 06:02 aillusions

I think the reason of this project not being released is because AWS SDK 1.2.x is not released yet as well. At the moment of writing it is 1.1.163.
However, I agree with you it shouldn't be stated in the README the dependency is 1.2.0. Then, we have to refer to maven central and find the last stable release is (at the moment of writing) 1.1.0.

May 31 '19 23:05 leandrodelsole

I agree it should be added into maven central.

Jul 09 '19 08:07 lalib

My observations:

(a) there is no tag for 1.2.0; only 1.1.0 exists. (b) the latest version in maven cental is 1.1.0 : https://search.maven.org/search?q=g:com.amazonaws%20AND%20a:dynamodb-lock-client&core=gav

#43 is a duplicate of this issue.

@amcp Are you able to tag & create a release for maven central?

Oct 28 '19 16:10 CandleCandle

1.1.0 requires "AmazonDynamoDB" for a builder, that can not be resolved or cast from DynamoDbClient. In version 1.2.0 it´s fixed. How it could be solved? There is no working documentation for that. Is the project really dead?

Sep 24 '21 15:09 akimkelar

We had to add FIXME in pom.xml as a temporary workaround:

        <dependency>
            <groupId>com.github.awslabs</groupId>
            <artifactId>amazon-dynamodb-lock-client</artifactId>
            <version>4b99836f7602d5e0691a5a6b27c7dba6886da901</version>
<!--FIXME folks from awslabs forgot to release version for AWS SDK 2.x, so we fetch version by commit hash -->
<!-- Latest available is 1.1.0, however master branch contains required 1.2.0 -->
<!--            <version>1.2.0</version>-->
        </dependency>
...
    <repositories>
        <repository>
            <id>jitpack.io</id>
            <url>https://jitpack.io</url>
        </repository>
    </repositories>

Seems like this temporary workaround will last forever