Fix the original JAR path check in the JarResultBuildStep #28259
Conversation
This file contains 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
…s different from the one in the POM's build section
quarkus-bot
bot
added
area/core
area/devtools
|
@aloubyansky should it be backported to 2.13? |
aloubyansky
added
triage/backport-2.13
and removed
area/core
area/maven
area/devtools
This comment has been minimized.
This comment has been minimized.
aloubyansky
added
area/core
area/maven
area/devtools
gsmet
approved these changes
Sep 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix the original JAR file check when the
finalNamein the Quarkus plugin is different from the one in the POM's build section. The consequence of this broken check was that the Quarkus runner JAR wasn't installed/deployed in the Maven repo.