[Build] Fix the manifest target and source information for jdbc projects #121888
Conversation
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
The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before
breskeby
added
>non-issue
:Delivery/Build
|
Pinging @elastic/es-delivery (Team:Delivery) |
mark-vieira
approved these changes
Feb 6, 2025
💔 Backport failedThe backport operation could not be completed due to the following error: You can use sqren/backport to manually backport by running |
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2025
…cts (elastic#121888) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
This was referenced Feb 11, 2025
Merged
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2025
…cts (elastic#121888) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2025
…cts (elastic#121888) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2025
…cts (elastic#121888) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2025
…cts (elastic#121888) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
breskeby
added a commit
that referenced
this pull request
Feb 12, 2025
…cts (#121888) (#122240) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
that referenced
this pull request
Feb 12, 2025
…cts (#121888) (#122237) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
that referenced
this pull request
Feb 12, 2025
…cts (#121888) (#122239) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
that referenced
this pull request
Feb 12, 2025
…cts (#121888) (#122238) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
breskeby
added a commit
that referenced
this pull request
Feb 13, 2025
…cts (#121888) (#122236) The nebula info broker plugin takes the information for the manifest from the java project settings rather then from the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project configuration accordingly. Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before (cherry picked from commit 6e6e42f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The nebula info broker plugin takes the information for the manifest from the java project settings rather then from
the compile task configuration. Instead of setting the compiler task configuration explicitly we now set the project
configuration accordingly.
Also tweaked the javaTestCompile tasks to keep compiling with general minimum runtime version as we did before.