spi dependencies check must not have scope 'provided'

[Narcasserun]

-I'm doing the data source plug-in transformation now. I put the public code generated by the data source plug-in loading and connection object in the Dao module, but the default SPI dependencies check package check plug-in does not allow the provider scope dependency other than the SPI module. In my opinion, it's reasonable for the plug-in to rely on the scope of provide and will not package the Dao module.

-If the packaging check is a matter of principle, I can only separate a datasource API module based on Dao and let each data source plug-in introduce the datasource API module (connection pool, spring dependency + some general code), so that there will be datasource API dependency under each data source plug-in, just like the task plugin implementation, However, the scenario is obviously not very suitable for data source plug-in loading. The reason is that some data source related dependencies will be packaged and loaded repeatedly, because the API module and server module will load the environment (Dao module) that the data source plug-in depends on by default. And there will be a little too loose coupling

What do you think of this problem?

Screenshot of the dependency of the sqlserver data source plug-in I implemented:

Screenshot of task shell plug-in dependency

[ruanwenjun]

@Narcasserun For better discuss, please use English.

[Narcasserun]

I have expressed it in English