Set the lower boundary of the default range for Quarkus platforms to 1.0.0.CR2 #5605
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
…ed Quarkus platforms to 1.0.0.CR2
aloubyansky
added
backport?
area/platform
gsmet
approved these changes
Nov 19, 2019
|
Merging per our discussion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Due to recently introduced changes in the project templates used for project generation and updates, it'll be safe to move the lower boundary of the default range of Quarkus platforms discovered by the tooling to the upcoming version 1.0.0.CR2.
Note that 1.0.0.CR2 has not yet been released, so the SNAPSHOT version of the tooling will now be falling back to the bundled version of the platform (which is based on quarkus-bom, SNAPSHOT) until 1.0.0.CR2 has been released and available in the remote repos.