Fix issue with updating core with a patch number other than 0 #19377
+2
−3
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
While researching opensearch-project/opensearch-build#5720, I ran into an issue where I could not version bump the core to 3.3.1 and run
./gradlew localDistro
successfully. It would run into the following error:The reason for this is that it hit this block which is only triggered when the minor and patch version are both non-zero. When the patch number is 0 (as it is with any minor version bump) then the condition never gets triggered.
This PR resolves the issue by removing references to the Legacy ES version numbers which are more than 2 major versions in the past at this point.
Related Issues
Related to opensearch-project/opensearch-build#5720
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.