-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
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
Refactor SPI interfaces - use single common ConfigExtension to ServiceLoad all avaje-config extensions #149
Conversation
I don't think this is what we want. Those methods were specifically on ConfigurationLog for a reason so its unclear why you moved them? If we where to make such a change we should communicate it clearly (and as such our github issue title should reflect all the change included in a PR). Why did you want to include this change? Resolved. |
avaje-config/src/main/java/io/avaje/config/CoreConfigurationBuilder.java
Outdated
Show resolved
Hide resolved
avaje-config/src/main/java/io/avaje/config/ConfigurationLog.java
Outdated
Show resolved
Hide resolved
As this is replaced by the generated one for ConfigExtension
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