Gradle will repeatedly try to import some stuff but it wont recognise most of the code so there's a mess. When migration is in process, if this is on, you'll never get rid of red highlited code no matter if there is an error or not. You want to have latest version of gradle plugins since maybe there were some improvements or fixes regarding kotlin DSL Before getting hands dirty, let's do some preparation inside of our existing gradle file. But the most important and tricky part of this migration is application's gradle file. Before getting our hands dirtyįor now we have created some packages, added some files, we are getting idea how the things should look.

More the flavours you have, bigger difference you'll see. This file is important because it can reduce the size of main gradle file a lot. One thing is sure, buildConfigField takes triple containing type, name and value which is perfect job for Kotlin's Triple type. It is used to manage all the properties that your project flavours need. This file does not have a generic format, it depends on your project. gradle and build generated directories)Ĭopy them from here and add them into buildSrc directory. It is used to add kotlin dsl dependency into this package. Last modified on Mon Disclaimer: Do not migrate to Kotlin DSL if you have gradle version You'll see this naming in other gradle files, this one is in the root (buildSrc).

Buildconfigfield