Refactor SPI interfaces - use single common ConfigExtension to ServiceLoad all avaje-config extensions #149
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 is a breaking change for avaje-config extensions.
Makes one super interface
ConfigExtension
for all the spi classes. All avaje-config extensions need to register with ServiceLoader using this interface rather than the specific one (like ConfigurationSource).All these extensions are loaded via ServiceLoader via the
ConfigExtension
interface rather than making the 6 separate service loader calls for each specific extension interfaces.Requires avaje/avaje-spi-service#18