CalvinKirs commented on issue #6612: URL: https://github.com/apache/dolphinscheduler/issues/6612#issuecomment-952785843
> > > Hi @CalvinKirs I'm a little confused about that is it going to be the same problem for the registration center and alarm center if we use Java native SPI, such as class conflicts and multi-version isolation? > > > > > > This kind of situation usually occurs in complex plugs-in, and it is mandatory to rely on two versions of the same jar. Such as our task module. > > But for simple modules, this is controllable. I see that other projects do not have any major problems in the registry, but the alarm is actually simpler, nothing more than HTTP or other more complicated communication methods, but the dependence is usually stable. > > What do you think? > > I think it's OK, and is it easy to swith another SPI way if we want it? Of course, this is just a modification of the plug-in loading method, and user extension plug-ins do not need to care.:) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
