gradlew

Findbugs fails with “java.io.IOException: No files to analyze could be opened”

血红的双手。 提交于 2019-12-10 09:59:38
问题 I run an Android Studio v2.1.3 and use ./gradlew build to detect errors in the Android project with the Findbags. Recently an error started to come up: FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':process:customFindbugs'. > java.io.IOException: No files to analyze could be opened There are enough disk space and RAM and beside that I don't see any particular reason for that error to occur. Please help to elaborate on this problem. 回答1: If you use 3.2,

Findbugs android gradle plugin

…衆ロ難τιáo~ 提交于 2019-12-09 05:36:05
问题 I have an android project. I want to introduce findbugs in my project as a gradle plugin. I tried to edit the project's build.gradle as below. buildscript { repositories { mavenCentral() maven { url 'https://maven.fabric.io/public' } } dependencies { classpath 'com.android.tools.build:gradle:1.0.0+' classpath 'io.fabric.tools:gradle:1.+' } } apply plugin: "java" apply plugin: "findbugs" findbugs { toolVersion = "2.0.1" sourceSets = [sourceSets.main] ignoreFailures = false reportsDir = file("

Task 'publishApkRelease' not found in root project

ぐ巨炮叔叔 提交于 2019-12-08 22:30:45
问题 Im trying to configure gradle-play-publisher in my project, I have configured play block in build.gradle(Module: app), here's my build.gradle(Module:app): apply plugin: 'com.android.application' android { compileSdkVersion 22 buildToolsVersion "23.0.0 rc2" defaultConfig { applicationId "com.***.***" minSdkVersion 11 targetSdkVersion 21 ndk { moduleName "mupdf" } } signingConfigs { release { storeFile file("./***") storePassword "***" keyAlias "***" keyPassword "***" } } buildTypes { release {

How to write Gradle startup script

蓝咒 提交于 2019-12-08 06:11:15
问题 I have a Gradle app that I startup using ./gradlew run . This works fine, but I'm trying to deploy to an AWS instance (Ubuntu 12) and I would like the script to execute on boot. I tried writing a startup.sh file with the above command, but no dice. I've also tried adding the command to the /etc/rc.local file, but that doesn't seem to work either. Can someone give me an idea as to how to execute `./gradlew run' on startup? Thanks! 回答1: I wrote the following init script for starting gradle

Gradle publish attemps to upload RPM to Artifactory YUM repo twice, second time fails with 403

白昼怎懂夜的黑 提交于 2019-12-08 01:08:51
问题 I'm trying to publish an RPM artifact to a local YUM repo on Artifactory using gradle and the ivy-publish plugin. The issue I'm having is that the publish tasks appears to attempt to upload the artifact twice, and the second attempt fails (correctly) with a HTTP status code of 403. The artifactory user I authenticate with has deploy/cache privileges but not delete. My question is why is the publish task attempting to upload the artifact twice? I include my gradle configuration and an extract

Gradle build hanging when jackOptions is enabled for Java 1.8

柔情痞子 提交于 2019-12-07 12:23:07
问题 I want to use lambdas in my project so I decided to switch to Java 1.8. Android Studio (2.1.3) forced me to enable jackOptions. Also I did install Java 1.8 on my mac and when I run javac -version in terminal I get javac 1.8.0_101 and the JDK in android studio points to the right one. When I try to build my project, gradle gets stuck on: :app:compileDebugJavaWithJack I did the following and nothing worked: gradlew clean git clean -fdx and reimport the project gradlew --stacktrace assemble If I

Gradle application plugin: Modify workingDir property

空扰寡人 提交于 2019-12-07 11:58:54
问题 I simply want to modify the directory where the program is run. Normally, it's run from the project root, which annoys me a little bit, because testing the program out can be quite annoying, since my program generates files and folders where it is being run. A JavaExec task has a property called JavaExec#workingDir, which would be this exact property I wanted to modify to something different of my choice. My question is: How do I modify the gradle run task in order to access this property?

Gradle build is hanging without failure, DefaultFileLockManager acquiring and releasing lock on daemon addresses registry

☆樱花仙子☆ 提交于 2019-12-06 12:32:43
I have several gradle-based projects and on all of them recently I've become unable to execute a ./gradlew clean build. Upon running this, the When I run with the --debug flag, I get stuck on "> Building 7% > :compileJava > Resolving dependencies ':compileClasspath'" and it never moves forward. When I ran with the --debug flag, I got this output regarding the DeafultFileLockManager acquiring and releasing a daemon lock, but this has been unhelpful. Here is the last bit of the gradle debug log that I see. 11:22:57.079 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager]

why gradlew :app:dependencyInsight failed?

瘦欲@ 提交于 2019-12-06 07:12:24
问题 I try to run this command to list all the dependencies of firebase-messaging library : gradlew :app:dependencyInsight --configuration compile --dependency firebase-messaging but it's return me : :app:dependencyInsight No dependencies matching given input were found in configuration ':app:compile' BUILD SUCCESSFUL in 0s 1 actionable task: 1 executed this is my build.gradle file : apply plugin: 'com.android.application' android { compileSdkVersion 27 defaultConfig { applicationId "com.example

Gradle application plugin: Modify workingDir property

大憨熊 提交于 2019-12-06 01:49:44
I simply want to modify the directory where the program is run. Normally, it's run from the project root, which annoys me a little bit, because testing the program out can be quite annoying, since my program generates files and folders where it is being run. A JavaExec task has a property called JavaExec#workingDir , which would be this exact property I wanted to modify to something different of my choice. My question is: How do I modify the gradle run task in order to access this property? You can access a property of a task by using tasks.<TaskToModify>.property = YourValue . So, in this