build.gradle

After I update Android Studio to 3.2.1 and gradle version in my project I am getting following build error. I have already checked lots of questions related this question but no luck. Project dependency Build.gradle buildscript { repositories { google() mavenCentral() maven { url 'https://maven.google.com' } gradlePluginPortal() jcenter() } dependencies { classpath 'com.android.tools.build:gradle:3.2.1' // NOTE: Do not place your application dependencies here; they belong // in the individual module build.gradle files } } allprojects { repositories { google() maven { url "https://jitpack.io" }

I did search a lot but unfortunately couldn't get it to work. Based on my search I found that I need to add following code into build.gradle file. However, Gradle seems doesn't recognize it and always says Geadle DSL method not found: test() test { testLogging.showStandardStreams = true testLogging.events("passed", "skipped", "failed", "standardOut", "standardError") afterTest { desc, result -> println "Executing test ${desc.name} [${desc.className}] with result: ${result.resultType}" } } Update I can confirm above code or better than that following code is working fine if you create a test

I was trying to integrate my project in android studio. but i am little confused when adding dependencies. I don't know which one is works good.I have tried Compile fileTree and compile files.Its not working for me . I found some methods.can any one tell me which one is appropriate for adding library (jar file only like admob). compile fileTree(dir: 'libs', include: '*.jar') compile 'com.android.support:appcompat-v7:+' compile project(":libraries:libraryname") compile files('libs/libraryname.jar') can any one tell me which one is appropriate for adding library (jar file only like admob). If

I am looking to add Groovy support to an existing java project so that I can seemlessly compile mixed Java and Groovy code using invokedynamic so that I can get Java-like execution speed without needing to waste excessive amounts of time with verbose Java syntax After reading that the gmaven plugin no longer supports compilation -and that the groovy eclipse compiler plugin doesn't yet support invokedynamic , I asked myself, why would I want to continue using Maven if it compiles Groovy code that is needlessly slow? Consequently, I decided I would try scrapping maven for Gradle so that I could

for example, read the json file in build.gradle and use the json values as strings in the file { "type":"xyz", "properties": { "foo": { "type": "pqr" }, "bar": { "type": "abc" }, "baz": { "type": "lmo" } } } I need to call properties.bar.type and abc should be replaced there. I need to convert these values to string and use in build.gradle file Crazyjavahacking From Gradle you can execute any Groovy code and Groovy already has build-in JSON parsers. E.g. you can use a task that will print your value into stdout: task parseJson { doLast { def jsonFile = file('path/to/json') def parsedJson = new

After building my final output file with Gradle I want to do 2 things. Update a local version.properties file and copy the final output final to some specific directory for archiving. Let's assume I already have 2 methods implemented that do exactly what I just described, updateVersionProperties() and archiveOutputFile() . I'm know wondering what's the best way to do this... Alternative A: assembleRelease.doLast { updateVersionProperties() archiveOutputFile() } Alternative B: task myBuildTask(dependsOn: assembleRelease) << { updateVersionProperties() archiveOutputFile() } And here I would call

I'm likely overlooking something pretty core/obvious, but how can I create a task that will always be executed for every task/target? I can do something like: task someTask << { println "I sometimes run" } println "I always run" But it would be much more desirable to have the always running part in a task. The closest I've come is: task someTask << { println "I sometimes run" } println "I always run" void helloThing() { println "I always run too. Hello?" } helloThing() So, using a method is an 'ok' solution, but I was hoping there'd be a way to specifically designate/re-use a task. Hopefully