Change io.quarkus.security:quarkus-security dependency to io.quarkus.security:quarkus-security-api #40465
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.
Fixes #40417.
Depends on quarkusio/quarkus-security#41.
This PR changes
io.quarkus.security:quarkus-security
dependency toio.quarkus.security:quarkus-security-api
.I've removed the old
io.quarkus.security:quarkus-security
dependency from some extensions whereio.quarkus:quarkus-security
, orio.quarkus:quarkus-security-api
orio.quarkus:quarkus-security-runtime-spi
already exist.As far as relocations are concerned, Quarkus core extensions are most likely the only consumers of the old
io.quarkus.security:quarkus-security
dependency. Any extension in Quarkus or Quarkiverse or elsewhere, if it needs it, shoud get it indirectly fromio.quarkus:quarkus-security
, orio.quarkus:quarkus-security-api
orio.quarkus:quarkus-security-runtime-spi
or other security and vert.x extensions which depend on it.The
relocations
in the core repository manages the relocation from theio.quarkus
group. If it is really needed then it would have to be added as part of quarkusio/quarkus-security#41.