Hi Community, Currently we have a dubbo-spi-extensions repo[1] to contain some infrequently used extensions which is also not necessary to remove from dubbo. Such as some customized cluster implementation is only used when healthy checking, and there are some users who really depend on this implementation. dubbo-spi-extensions repo is a good choice for these implementations, which will not affect apache/dubbo for most users and provide a pluggable way if users need it.
Thanks for @haoyann hard work, we can make sure that dubbo-spi-extensions can work fine with ExtensionLoader. However, there are some questions should be resolved: 1. How can we define an extension that is needed to move to dubbo-spi-extensions while it is in apache/dubbo repo now? 2. How can we define the version of these sub projects? If we make these sub projects the same version at a time, we need to publish the whole repo timing, so we can make sure the extensions are up to date. Such as a month? If we make these sub projects having different versions, how can we publish only one of them if needed? Do you have any suggestions? [1] https://lists.apache.org/thread.html/r9248ffdc11716d5e1089911652ef69eb39ec33aeeda133e6b5c2e441%40%3Cdev.dubbo.apache.org%3E Albumen
