We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarkus will probably deprecate quarkus-bom-deployment and merge its content into quarkus-bom [1], should we do the same ?
[1] quarkusio/quarkus#10182
The text was updated successfully, but these errors were encountered:
Let's wait for the result of the discussion on quarkus-dev ML.
Sorry, something went wrong.
The chance that the deployment BOM is going to survive is close to zero now.
The relevant discussions, for the record:
Quarkus is keeping their deployment BOM as an alias of their runtime BOM.
I guess we can remove the deployment BOM, because we are not assuming any third party depends on it?
We are not yet a 1.0 so - IMHO - we can safely do such kind of changes
Fixed via 4810732
ppalaga
No branches or pull requests
Quarkus will probably deprecate quarkus-bom-deployment and merge its content into quarkus-bom [1], should we do the same ?
[1] quarkusio/quarkus#10182
The text was updated successfully, but these errors were encountered: