Using this configuration is not strictly required for annotation processing itself to work ( provided or even compile in some cases also do the job). This scope is dedicated to annotation processors like dagger-compiler from Dagger 2. ![]() What phase means here? Let’s take a look a the Figure 1. The scope is related to phase when the configuration is used. There are also wearApp configurations related to Android Wear, they are not covered by this article. Note that currently (up to Gradle plugin 2.2.0) only one build type can be instrumentation-tested, so there are no corresponding debug and release configurations. From configurations point of view androidTest is treated as a build type. Unit test configuration inherits from regular ones (inheritance is described later in this article).įinally, there is a androidTest configuration group used for instrumentation tests (running on device/emulator). Each regular configuration has also corresponding unit test one, so by default for compile there is also testCompile, testDebugCompile and testReleaseCompile. compile is applicable to both debug and release build types. ![]() If there is no prefix configuration is common to all build variants, eg. in debugCompile: debug is a build type (equal to build variant when there are no product flavors) and compile. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |