Dependencies added programmatically by plugins are detected by the migration

[martinbonnin]

Dependencies such as com.squareup.sqldelight:runtime-jvm or org.jetbrains.kotlin:kotlin-android-extensions-runtime aree added by their respective plugins and therefore do not need any manual intervention by the users

[LouisCAD]

There's no way to ensure the dependencies have been added by a plugin or by code in the build files.

That means there's a need for rules for every case to be handled. If the cases where we do this is limited, we can embed these rules, but there might be some that are very special cases.

Do you think we should provide an API to allow that to be user defined?

[LouisCAD]

I think this issue is not happening with the new refreshVersionsMigrate Gradle task.

I think we'll soon drop the original fully manual migration task in favor of the aforementioned refreshVersionsMigrate Gradle task, which will make this issue obsolete.