Ensure Java compile module path is tracked as a task input#87064
Merged
elasticsearchmachine merged 1 commit intoelastic:masterfrom May 23, 2022
Merged
Conversation
Collaborator
|
Pinging @elastic/es-delivery (Team:Delivery) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This is a follow up to #81066 which ensures that we track the module path as a input on Java compilation tasks. Since we truncate the compile classpath and pass the module path as separate CLI arguments we need to track those separately. We do that by simply annotating a getter on the
CommandLineArgumentProvider.