![Android studio gradle version 5.4.1 what gradle is this](https://cdn1.cdnme.se/5447227/9-3/screenshot_8_64e62948e087c31b4a9aa5ed.jpg)
![android studio gradle version 5.4.1 what gradle is this android studio gradle version 5.4.1 what gradle is this](https://raw.githubusercontent.com/telerik/platform-friends-android/master/screenshots/android-login-screen.png)
Tip: remember that you can type gradle aJ to run the assembleJnidebug task.
![android studio gradle version 5.4.1 what gradle is this android studio gradle version 5.4.1 what gradle is this](https://3.bp.blogspot.com/-9hVtUJjQiXY/WpaSHFSD3cI/AAAAAAAAD_k/k3hJX841vtsRRpmIG97qtHVZEuM2Z65nQCLcBGAs/s1600/Untitled_document18.png)
According to this rule, adle snippet above will also generate an assembleJnidebug task, and assemble would be made to depend on it the same way it depends on the assembleDebug and assembleRelease tasks. When the debug and release Build Types are pre-created, their tasks are automatically created as well. The assembleDebug and assembleRelease tasks have already been mentioned, and this is where they come from. This means the Build Type names cannot be main or androidTest (this is enforced by the plugin), and that they have to be unique.Īdditionally, for each Build Type, a new assemble task is created, e.g. src/debug/java directory can be used to add sources that will only be compiled for the debug APK. In addition to modifying build properties, Build Types can be used to add specific code and resources. For each Build Type, a new matching sourceSet is created, with a default location of src//, e.g. See the DSL Reference for a list of all properties that can be configured on a build type.
![Android studio gradle version 5.4.1 what gradle is this](https://cdn1.cdnme.se/5447227/9-3/screenshot_8_64e62948e087c31b4a9aa5ed.jpg)