buildevents | A small helper to generate Honeycomb traces from CI builds

I am trying to read versionCode and versionName from a properties file (which I seem to be able to do), and use those values when declaring the Android versionCode and versionName (which does not seem to work).

build.properties

I am running into issue of building my project. It used to work fine, but when I build it now it fails on shadowJar task, with a class not found exception. No dependency got added. It used to work with Gradle 3.3, but now when I try with gradle 4.10, it keep failing with below error. Also If I remove line "mergeServiceFiles('META-INF/services')", then this exception doesn't occur.

This is my task definition

After installing the marketplace plugin I'm following the official documentation for my SonarQube installation (8.6 Community)

gradle plugin cfg:

We have been testing the upgrade process for MarkLogic Server - going from Server v9.0-8.2 to v10.0-5.2 , then the data hub going from v4.1.1 -> v4.3.2 , then to v5.2.6

This is running on a windows 2016 server.

Java 1.8.0_271-b09 is installed

Gradle 5.1.1 is installed

The ML server upgrade went fine.

The Data Hub upgrade from 4.1.1 to 4.3.2 went fine.

The upgrade from 4.3.2 to 5.2.6 - we have an issue, this is the commannd and the error :

gradlew.bat hubUpdate -PmlUsername= un -PmlPassword= pw -i --debug

I recently migrated to firebase-crashlytics-gradle from the deprecated Fabric library. It works properly on the local machine with these commands:

I investigated this post, but it doesn't help me.

My task is to generate javadoc only for specific classes.

when id update android studio to 3.6 android gradle tools to 3.6.0 ,there is a problem.when I generate sign apk,I got an exception，it is like this

I try to run my React Native app in an android emulator on a fresh Ubuntu 18.04 installation.

In Android studio, gradle build failed with this error :

I’m currently reading a tutorial page of Spring Boot (https://spring.io/guides/gs/uploading-files/#initial) in order to check how to upload an image file, but I don’t quite understand the “Build an executable JAR” part of “Run the Application” Chapter.

I downloaded the project via the link on the tutorial’s page, and copied and pasted all the files, and I wrote “./gradlew bootRun” on the command prompt, just as written in the Build an executable JAR part of the page, but I’m unable to run the program.

To describe my situation in a more concrete way, I moved to the directory where there is a gradle file (in my PC environment, it’s C:\Users\marra\Documents\workspace-spring-tool-suite-4-4.5.1.RELEASE\ImgUpload\gs-uploading-files\initial ) by cd command, and then wrote “./gradlew bootRun” and hit the Enter button of the keyboard, but still just get an error message “BUILD FAILED”.

Here I come up with 2 questions.

・First of all, am I properly following the tutorial’s instructions in the first place? In other words, what I did is “move to the C:\Users\marra\Documents\workspace-spring-tool-suite-4-4.5.1.RELEASE\ImgUpload\gs-uploading-files\initial directory and wrote “./gradlew bootRun” and hit the Enter”, but was this the right way of running the tutorial’s program? If my way of doing it is wrong, how should I have run the program? What does “you can run the application by using ./gradlew bootRun” mean?

・Another possibility of this failure is that I get an error message even though I do follow the tutorial’s instructions properly. But in that case, which part did I do wrong? When I try to run the program and it fails, the command prompt shows an error message “Execution failed for task ':compileJava'. > Compilation failed; see the compiler error output for details.”. I did some research by myself, and for example on a page like https://github.com/realm/realm-java/issues/5910 suggests that “Any compilation failure gets this message.”. Perhaps I might not have copied and pasted all the sample code of the files properly, but the problem is that I don’t know which folder’s which file’s which line to check. I added “--debug” to the “./gradlew bootRun” command to see what kind of errors I get, and I got the following.