chore(ci): Fix circular dependency in dynamodb-local and maven packaging phases #2129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR address a small issue where a circular dependency in Maven phases caused build issues for the idempotency utility when attempting to start dynamodb-local before unit tests on an initial
mvn -B test
command.The issue is:
${project.build.directory}/dynamodb-local
before running unit tests.powertools-idempotency-core
)powertools-idempotency-core
and failsSolution:
powertools-idempotency-core
is not needed for DynamoDB local which is treated as an external process. Removing it solves the circular dependency.Example failure: https://github.com/aws-powertools/powertools-lambda-java/actions/runs/17577454233/job/49925991193
Changes
Issue number: #2128
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.