fix: add Quarkus plugin deprecation #153
Merged
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
acornett21
approved these changes
Jul 29, 2024
metacosm
approved these changes
Aug 7, 2024
xstefank
force-pushed
the
plugin-deprecation
branch
2 times, most recently
from
c303b69
to
a97164a
Compare
Signed-off-by: xstefank <[email protected]>
xstefank
force-pushed
the
plugin-deprecation
branch
from
a97164a
to
56c2927
Compare
xstefank
changed the title
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.
This will fix operator-framework/operator-sdk#6645.
We should deprecate the plugin nevertheless before we remove it from operator-sdk.
But it will be up to @metacosm, I think I can keep this running for a while. I'm still not sure how much people are used to operator-sdk workflow vs using custom tools to bootstrap their operators.