Fix circular dependency when ECLIPSELINK arg is set to true during build #284
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.
Description
When ECLIPSELINK arg is set to true during build, we will get the following build error:
This is introduced as part of e81a2c4#diff-f714fa5f754f0da54abb877f8cf4e3de6341ad321db5f4c697fa602a5da8e4b4.
Upon debugging, this is due to following in
extension/persistence/eclipselink/build.gradle.kts
This is added earlier where when building polaris-service with eclipse enabled, it was not picking up the dependencies. But as the change introduced above, that is now included but causing circular dependency.
Fixes # (280)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
After removed the line above, I then did 2 tests:
Test 1:
Check jar file to ensure all 3 classes are included in the final jar:
Test 2:
Ensure bootstrap still work when using persistent backend:
Checklist:
Please delete options that are not relevant.