-
Notifications
You must be signed in to change notification settings - Fork 217
Cleaup Test Dependencies #1332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleaup Test Dependencies #1332
Conversation
Signed-off-by: Siri Varma Vegiraju <[email protected]>
Signed-off-by: sirivarma <[email protected]>
Signed-off-by: sirivarma <[email protected]>
@siri-varma it seems that there are so missing classes after your POM changes and there some |
@artur-ciocanu Yes. Still working on fixing this |
Signed-off-by: siri-varma <[email protected]>
Signed-off-by: siri-varma <[email protected]>
Signed-off-by: siri-varma <[email protected]>
Signed-off-by: siri-varma <[email protected]>
@artur-ciocanu @salaboy @cicoyle This PR is ready to be reviewed. Thank you |
@artur-ciocanu do you have any comments about this? Because the Dapr SDK is split into two big things (modules and sdk-tests), I believe that it was ok to do dependency management separately, as dependencies needed in the sdk-tests are not needed in the SDK itself (like toxy proxy). But if we are moving towards a world where we have all the SDK tests as testcontainer tests, this makes sense. |
@siri-varma to be clear.. I am not against this.. I am just thinking a bit long term how this will work out. |
@salaboy quick comment, my intention of moving all of them to the base pom is so that we can have one single place to manage all the dependencies. However, this need not affect the SDK/testcontainer test choices is what I feel. Let me know if I am missing something. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@siri-varma the PR looks great, I have left some comments, could you please take a look.
Also could you please provide a high level overview what are you trying to achieve with dependency cleanup PRs. I see the value in extracting version properties, however I am not following why we have to move them from respective places to parent POM.
If I take grpc-testing example https://github.com/search?q=repo%3Adapr%2Fjava-sdk%20%22grpc-testing%22&type=code I may be seeing this through the lens of my experience, open to get @dapr-javasdk maintainer thoughts as well. |
Signed-off-by: siri-varma <[email protected]>
@artur-ciocanu/ @salaboy / @dapr/maintainers-java-sdk addressed all the comments. Thank you |
Signed-off-by: siri-varma <[email protected]>
…ri-varma/java-sdk into users/svegiraju/pom-cleanup-3
Signed-off-by: siri-varma <[email protected]>
Signed-off-by: Siri Varma Vegiraju <[email protected]>
Signed-off-by: Siri Varma Vegiraju <[email protected]>
@artur-ciocanu / @dapr-java-sdk-reviewer / @salaboy This PR is ready to be reviewed |
@artur-ciocanu / @dapr-java-sdk-reviewer / @salaboy Just a gentle reminder about this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for all this effort! 🙇
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1332 +/- ##
============================================
+ Coverage 76.91% 78.13% +1.22%
- Complexity 1592 1830 +238
============================================
Files 145 223 +78
Lines 4843 5663 +820
Branches 562 601 +39
============================================
+ Hits 3725 4425 +700
- Misses 821 917 +96
- Partials 297 321 +24 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #940
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: