Skip to content
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

[Backport] [1.2] [FEATURE] Add OPENSEARCH_JAVA_HOME env to override JAVA_HOME (#2040) #2042

Closed
wants to merge 1 commit into from

Conversation

reta
Copy link
Collaborator

@reta reta commented Feb 2, 2022

Signed-off-by: Andriy Redko [email protected]

Description

Backport of #2040 to 1.2

Issues Resolved

Closes #1872

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff

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.

@reta
Copy link
Collaborator Author

reta commented Feb 2, 2022

@dblock @andrross no objections from your side guys to bring it into 1.2? thanks!

@opensearch-ci-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Check failure 9accef3aed2050aac80464a337cf7a3500624177
Log 2191

Reports 2191

@reta reta force-pushed the issue-issue-1872.1.2 branch from 9accef3 to 8c90607 Compare February 2, 2022 21:10
@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Check success 8c90607
Log 2193

Reports 2193

@andrross
Copy link
Member

andrross commented Feb 2, 2022

I would think this change doesn't meet the definition of "hotfix" defined in the release policy. Do you have a particular reason for wanting to backport this to the 1.2 branch?

@reta
Copy link
Collaborator Author

reta commented Feb 2, 2022

I would think this change doesn't meet the definition of "hotfix" defined in the release policy. Do you have a particular reason for wanting to backport this to the 1.2 branch?

Thanks @andrross I don't have the compelling reasons for 1.2 (besides matching the original documentation section), no objections to close this backport, @dblock sounds good to you?

@dblock
Copy link
Member

dblock commented Feb 3, 2022

Agreed, let's close. Shipping this in 1.3.0 (1.x branch) is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants