-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Fix javaagent arg when running in IntelliJ #17886
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
Fix javaagent arg when running in IntelliJ #17886
Conversation
Taking the summary from my conversation with Claude to fix this: 1. We needed afterEvaluate to ensure the project was fully configured before accessing its properties 2. The correct path was in build/distributions rather than build/libs 3. We had to properly handle Gradle's Provider API when constructing the path 4. The jar name needed to include both the archivesName and the project version Signed-off-by: Michael Froh <[email protected]>
❕ Gradle check result for 70c774b: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17886 +/- ##
============================================
+ Coverage 72.43% 72.47% +0.03%
- Complexity 66789 66809 +20
============================================
Files 5449 5451 +2
Lines 309085 309146 +61
Branches 44979 44988 +9
============================================
+ Hits 223899 224041 +142
+ Misses 66906 66784 -122
- Partials 18280 18321 +41 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Taking the summary from my conversation with Claude to fix this: 1. We needed afterEvaluate to ensure the project was fully configured before accessing its properties 2. The correct path was in build/distributions rather than build/libs 3. We had to properly handle Gradle's Provider API when constructing the path 4. The jar name needed to include both the archivesName and the project version Signed-off-by: Michael Froh <[email protected]> Signed-off-by: Sriram Ganesh <[email protected]>
Taking the summary from my conversation with Claude to fix this: 1. We needed afterEvaluate to ensure the project was fully configured before accessing its properties 2. The correct path was in build/distributions rather than build/libs 3. We had to properly handle Gradle's Provider API when constructing the path 4. The jar name needed to include both the archivesName and the project version Signed-off-by: Michael Froh <[email protected]> Signed-off-by: Harsh Kothari <[email protected]>
Taking the summary from my conversation with Claude to fix this: 1. We needed afterEvaluate to ensure the project was fully configured before accessing its properties 2. The correct path was in build/distributions rather than build/libs 3. We had to properly handle Gradle's Provider API when constructing the path 4. The jar name needed to include both the archivesName and the project version Signed-off-by: Michael Froh <[email protected]> Signed-off-by: Harsh Kothari <[email protected]>
Description
Taking the summary from my conversation with Claude to fix this:
Related Issues
Resolves #17883
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.