gradlew

Poor performance of javafx ported app

由 梦想与她 提交于 2019-12-06 00:43:35
I just ported using gradlew into android a sample netbeans javafx project called "PuzzlePieces". The app has got soo poor performance, what can cause that? My device: LG E975, 4.4 kitkat José Pereda This question contains some possible reasons why performance on an Android device could be poor in terms of what one could expect based on how the app runs on desktop. Anyway, there is a quick win in "PuzzlePieces", and it is related to the CSS point mentioned in that question. The Desk class adds this inline styling: Desk(int numOfColumns, int numOfRows) { setStyle("-fx-background-color: #cccccc;

IllegalArgumentException: already added: Landroid/support/v4/accessibilityservice/AccessibilityServiceInfoCompat$AccessibilityServiceInfoIcsImpl;

由 喜你入骨 提交于 2019-12-05 23:32:02
问题 I'm using Android Studio + gradle on MyProject + Facebook api as a library. See below settings. I've tried removing all references of support-v4 (either r7 or 18.0.0) and replace them with support-v13, but the message with v4 was still present. I've also noticed that support-v4-r7 appears in External libraries, even though it's not referenced at all, anywhere. Would that be the problem ? MyProject build.gradle: buildscript { repositories { mavenCentral() } dependencies { classpath 'com

Why won't Android Studio create my AAR file in release mode

由 时光怂恿深爱的人放手 提交于 2019-12-05 17:33:34
Using Android Studio, I have an Android library project which produces 'library/build/outputs/aar/MyLIB.aar" just fine in Debug mode, but does not do so in Release mode. I see no errors, just "BUILD SUCCESSFUL" in the "Gradle Console" window but no Release Mode artifact. There was a similar question raised here , and I'm getting the same behavior as #user1624552 mentions in the link: "gradlew clean" followed by "gradlew aR" resultd in my AAR being created and correctly placed in the directory above. But using Android Studio and the "Release Mode" Build Variant does NOT create an AAR file. Is

Unable to run gradlew

由 痴心易碎 提交于 2019-12-05 14:35:46
问题 I've setup a build.gradle file with apply plugin: 'java' . I tried setting up a gradle wrapper using the instructions here, but when I type sudo ./gradlew build , I get an error sudo: ./gradlew: command not found . When I type gradle build , the project builds fine. It's just gradlew that isn't working. I even tried sudo chmod +x gradlew but it didn't work. I'm using Fedora 20, 64 bit and gradle version 1.10. 回答1: Ok so the solution was to run gradlew on the Linux partition itself. Somehow,

Android Studio Gradle version - Gradle version 2.8 is required

由 ≯℡__Kan透↙ 提交于 2019-12-05 05:38:18
问题 I'm trying to build an Android project but the following error occurred Error:(10, 1) A problem occurred evaluating project ':app'. > Failed to apply plugin [id 'com.android.application'] > Gradle version 2.8 is required. Current version is 2.4. If using the gradle wrapper, try editing the distributionUrl in C:\Users\...\gradle\wrapper\gradle-wrapper.properties to gradle-2.8-all.zip It seem something's wrong with the Gradle version, however I checked the gradle-wrapper-property and it's

What is the difference between gradlew build and gradlew assembleRelease

由 纵饮孤独 提交于 2019-12-04 17:06:27
问题 I want to build apk from command line with the help of gradle. Which command should I use to build apks for only release flavours? 回答1: Debug ./gradlew Release ./gradlew assembleRelease your gradle file should contains: android { [...] signingConfigs { release { storeFile file("../keystore.jks") storePassword "pwd" keyAlias "alias" keyPassword "pwd" } } buildTypes { release { signingConfig signingConfigs.release } } [...] } 回答2: You can run these commands: assemble - Assembles all variants of

Run application via gradlew with -Xmx and -Xms

由 谁说我不能喝 提交于 2019-12-04 16:26:46
问题 I have an application. I run it via gradlew run-app Or debug gradlew debug-app It works. How do I pass '-Xmx' argument into the application which I run (debug)? Is it possible to do so without edditing build.gradle file? I found this Gradle unknown command-line option '-X' I get a similar error when I try gradlew debug-app -Xmx2000m Error FAILURE: Build failed with an exception. * What went wrong: Problem configuring task :debug-app from command line. > Unknown command-line option '-X'. I

why gradlew :app:dependencyInsight failed?

由 白昼怎懂夜的黑 提交于 2019-12-04 11:44:57
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.test.myapplication" minSdkVersion 15 targetSdkVersion 27 versionCode 1 versionName "1.0"

Gradle difference between test and check

由 无人久伴 提交于 2019-12-04 08:50:45
问题 My build.gradle is as follows: group 'groupName' version 'version' apply plugin: 'java' apply plugin: 'idea' sourceCompatibility = 1.8 repositories { . . . } dependencies { . . . testCompile group: 'junit', name: 'junit', version: '4.12' } In Grade when doing ./gradlew tasks I receive Verification tasks ------------------ check - Runs all checks. test - Runs the unit tests. What is the difference between these two tasks? The output of ./gradlew check is identical to ./gradlew test .

IllegalArgumentException: already added: Landroid/support/v4/accessibilityservice/AccessibilityServiceInfoCompat$AccessibilityServiceInfoIcsImpl;

由 。_饼干妹妹 提交于 2019-12-04 04:13:39
I'm using Android Studio + gradle on MyProject + Facebook api as a library. See below settings. I've tried removing all references of support-v4 (either r7 or 18.0.0) and replace them with support-v13, but the message with v4 was still present. I've also noticed that support-v4-r7 appears in External libraries, even though it's not referenced at all, anywhere. Would that be the problem ? MyProject build.gradle: buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.5.+' } } apply plugin: 'android' repositories { mavenCentral() maven { url
订阅 gradlew