


The dependency is also available at compile time and runtime for the consumers of this library module. To be consistent with Gradle’s library plugin, Android plugin 2.5.0 is moving to these dependency configurations.Īpi : the dependency is available to the library module at compile time. Gradle 3.4 introduced a new java-library plugin that includes new configurations allowing control over publication to compile and runtime classpaths (for inter-module dependencies).

Code samples in the sections below also show you how to update your build configuration to work with the new plugin and only apply those configurations when you pass the command line argument from the previous section. The following sections describe changes to the build model in version 2.5.0. Alternatively, you can simply bypass the wrapper and use a local installation of stable Gradle by running with gradle, instead of. Note: If you want to switch to using the stable version of the plugin, make sure to also update gradle-wrapper.properties to use a stable version of Gradle.
