"Build successful" but "Error Building" for Java Library w/ Gradle 4.10.2

[tenbergen]

Dear all,

from one day to the next, builds started failing for https://github.com/tenbergen/anki-drive-java/ , which is a Java Library using Gradle 4.10.2.

We're using Gradle to build the Java sources and distribute it with Jitpack. Jitpack has been notoriously finicky with this project (see side note below), but the Java parts always built fine. Most recently, the release 0.1.5 build just like we wanted it: https://jitpack.io/com/github/tenbergen/anki-drive-java/0.1.5/build.log

However, from one day to the next, builds on new commits fail. Jitpack reports "Build successful" but also reports "Error Building," with no further details: https://jitpack.io/com/github/tenbergen/anki-drive-java/master-4e36b2a7e0-1/build.log

Even the same commit that we created release 0.1.5 from now fails (but was previously successful): https://jitpack.io/com/github/tenbergen/anki-drive-java/740dffb/build.log

So, something changed between May 9 (when we build 0.1.5) and now when we try to build (actually "now" means Friday May 15 when I first noticed this issue).

We did not change gradle.build nor jitpack.yml - all commits are just changes to the Java source. It builds fine locally on Mac, Ubuntu, Windows as well as in Tavis-CI: https://travis-ci.org/github/tenbergen/anki-drive-java/branches

Side note: I'm also using Gradle to build a nodeJS Bluetooth gateway that is part of the project (hence we're bound to 4.10.2), but don't really need Jitpack to build the Node components of the library. After some trouble over the past few months getting Jitpack to build Node properly, we gave up and are no longer building it. So, I guess we can ignore the Node parts of the project.

Another side note: I'm comparatively new to build systems, so mea culpa if this is a case of PEBKAC.

Thank you for your help!

--Bastian

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.