Skip to content

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

Merged
merged 1 commit into from
Apr 10, 2025

Conversation

msfroh
Copy link
Contributor

@msfroh msfroh commented Apr 10, 2025

Description

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

Related Issues

Resolves #17883

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

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.

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]>
Copy link
Contributor

❕ 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.

Copy link

codecov bot commented Apr 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.47%. Comparing base (1628152) to head (70c774b).
Report is 8 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions github-actions bot added the bug Something isn't working label Apr 10, 2025
@owaiskazi19 owaiskazi19 merged commit 11618fd into opensearch-project:main Apr 10, 2025
57 of 58 checks passed
rgsriram pushed a commit to rgsriram/OpenSearch that referenced this pull request Apr 15, 2025
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]>
Harsh-87 pushed a commit to Harsh-87/OpenSearch that referenced this pull request May 7, 2025
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]>
Harsh-87 pushed a commit to Harsh-87/OpenSearch that referenced this pull request May 7, 2025
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] IntelliJ local gradle build is broken post introduction of Java agent
2 participants