Closed fedinskiy closed 6 months ago
Same problem affects all amazon quickstarts: !amazon-dynamodb-quickstart,amazon-kms-quickstart,amazon-s3-quickstart,amazon-ses-quickstart,amazon-sns-quickstart,amazon-sqs-quickstart,amazon-ssm-quickstart
Things, that help:
quarkus-amazon-services.version
to 2.13.1 (this is done in main
branch)quarkus-amazon-services-bom
from quarkus.platform.group-id
and not from io.quarkiverse.amazonservices
(this is done in code.quarkus)@aloubyansky I can prepare a fix for this issue, but I need to know, which way is preferred: upgrading to 2.13.1 or using platform instead of quakiverse.
Always using the platform BOM
if it's a compatible version upgrade then we should consider it too
The downside of using the platform BOM property is it won't be testable with io.quarkus
as the platform groupId though. But otherwise that's how it should be.
@aloubyansky documentation[1] for these extensions says "A newer version of this extension has been released with the group id io.quarkiverse.amazonservices", so I presume, that using the io.quarkus.platform version is not recommended anymore.
The fix is here: https://github.com/quarkusio/quarkus-quickstarts/pull/1407
[1] https://quarkus.io/extensions/io.quarkus/quarkus-amazon-sqs/
The groupId of the extension artifacts is still the quarkiverse one. The quarkiverse BOM though is not aligned with the platform, so as long as a user is interested in using a dependency aligned version of the BOM for these extensions, the platform BOM should be used.
Go it, switched to io.quarkus.platform
Too late, the previous version got merged :)
I use branch 3.8
Steps to reproduce:
sdk use java 17.0.10-tem
mvn clean verify -Dquarkus-plugin.version=3.8.3 -Dquarkus.platform.version=3.8.3 -pl amazon-dynamodb-quickstart/
— successful build in ~minutesdk use java 21.0.2-tem
mvn clean verify -Dquarkus-plugin.version=3.8.3 -Dquarkus.platform.version=3.8.3 -pl amazon-dynamodb-quickstart/
Fails with the following error: