gradle-plugin

I'm currently trying out the Firebase analytics suit, but, i have faced one small issue, my app is distributed on both google play and amazon store (which doesn't support google play services), so for the amazon flavor i want to remove the dependency to Firebase (which i already know how to do), but, i also need to remove the Firebase plugin, so that it doesn't throw an exception while building. This is what i have as far now: productFlavors { google { applicationId 'google app id' } amazon { applicationId 'amazon app id' } } dependencies { googleCompile 'com.google.firebase:firebase-analytics

The latest version (3.0.0) of the Android Plugin for Gradle has broken its API for manipulating Variant Outputs . This API was used for manipulating files creating during builds (such as AndroidManifest.xml), and has been removed to improve configuration times. What new APIs are available to manipulate Variant Outputs, and how do they differ to the 2.X APIs? The changes to outputFiles has now been documented on the Android Developer site . Essentially, instead of accessing the outputFile directly from the gradle API, the recommendation is to access the directory containing the file instead.

when upgrading to android-studio 3.4.x/gradle build plugin 3.4.x /gradle 5.3 ... wondering if its an issue with the android plugin. ERROR: No value has been specified for property 'manifestOutputDirectory'. My gradle script does not use manifest related variables, nor has it changed the manifest. The version before my upgrade is Android-Studio: 3.3/Gradle pulgin: 3.3.2/Gradle: 5.3 First Update(20190508)：Fix method(temporary) Find a temporary fix method, but the method of correcting the error is still unknown. Ways to avoid: I am a Mac OS X system: Click Android Studio->Preperences...-

Is there a difference except that: apply from: - gets the (plugin).gradle from a URL apply plugin: - gets the (plugin).gradle from the gradle plugin server Amnon Shochot The actual difference between apply from: and apply plugin: is that the former is to be used for script plugins given a path to the local file system or a URL to a remote location, and the latter is used for binary plugins using the plugin id. You can read more about it in Gradle documentation here . apply from: calls the script directly as if it was part of the build file See https://docs.gradle.org/current/userguide/plugins

I have an apparent conflict with firebase 11.8.0 and google-services plugin 3.1.2. The build fails recommending that I use version 11.4.2 of firebase instead. Relevant extracts of my gradle build files: Root build.gradle buildscript { repositories { google() ... } dependencies { classpath 'com.google.gms:google-services:3.1.2' ... } } app build.gradle : apply plugin: 'com.google.gms.google-services' repositories { google() .... } dependencies { implementation "com.google.firebase:firebase-core:11.8.0" .... } I've correctly generated the firebase app files: ./app/src/debug/google-services.json

I'm pretty new to working with Gradle and I'm trying to develop a plugin that helps manage version numbering. This plugin defines a task that sets the project.version property of the project it's applied to. What I'm trying to do is make it so that this property is set at the start of every Gradle build. Using Peter's answer to another Gradle question , I've managed to get my task to execute before any other by adding gradle.startParameter.taskNames = [":setProjectVersionNumber"] + gradle.startParameter.taskNames within my plugin's apply method. However, other plugins (notably 'Maven-publish')