This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
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.
Support ES version 7.7.0 #58
Support ES version 7.7.0 #58
Changes from 18 commits
e8d9f03
d20befa
f91d338
3cf52f2
7b3f6fd
942b354
bd06eb6
4f22946
2eb846b
ae47e57
64220cb
2033c8a
5e53b91
534f73a
04b805a
0a5953f
8bc562d
6185f6d
b0e65c0
8a49766
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Can we make this a bit more reliable by checking if the sample plugin comes before job scheduler plugin and if so then removing/adding? Otherwise if it changes again next version this will break again.
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.
I think I can make this change in this version. There is no doubt it will make the plugin installation order much more reliable, but is not that important. The whole
afterEvaluate
block is a temporary workaround, and I believe the plugins should not be installed in this way forever, so theafterEvaluate
block won't last long. An ideal case is in next version, thetestClusters
Gradle plugin get changed and this problem get fixed, and this gradle file get restored.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.
Looking forward to hear opinions from other reviewers as well.