https://bugzilla.redhat.com/show_bug.cgi?id=1247385

--- Comment #1 from Orion Poplawski orion@cora.nwra.com --- I working with jabref (https://github.com/JabRef/jabref). I'll post my issues here in case they make good items for the HowTo.

First issue seems to be that it wants to package up a jar with all deps using "fatjar":

// enables fatjar, the creation of a jar with all dependencies bundled inside buildscript { repositories { jcenter() } dependencies { classpath 'eu.appsatori:gradle-fatjar-plugin:0.2' } } apply plugin: 'fatjar' fatJar { classifier 'fat' manifest { attributes 'Main-Class': "net.sf.jabref.JabRefMain" } }

So presumably we want to change this to a standard jar mechanism? For now I've simply removed this whole section.

Next issue:

+ gradle-local

FAILURE: Build failed with an exception.

* Where: Build file '/builddir/build/BUILD/jabref-v_2.11b3/build.gradle' line: 81

* What went wrong: A problem occurred evaluating root project 'JabRef'.

Could not import Ant build file '/builddir/build/BUILD/jabref-v_2.11b3/build-wrapper.xml'.

Using the --stacktrace option showed that the issue was a missing jarbundler:

/builddir/build/BUILD/jabref-v_2.11b3/build.xml:522: taskdef class net.sourceforge.jarbundler.JarBundler cannot be found

However, adding BR jarbundler doesn't appear to help.

https://bugzilla.redhat.com/show_bug.cgi?id=1247385

Mikolaj Izdebski mizdebsk@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED

--- Comment #3 from Mikolaj Izdebski mizdebsk@redhat.com --- I've just added initial section about Gradle and I will look into expanding it in future. https://fedorahosted.org/released/javapackages/doc/#gradle

https://bugzilla.redhat.com/show_bug.cgi?id=1247385

--- Comment #5 from Mikolaj Izdebski mizdebsk@redhat.com --- (In reply to Orion Poplawski from comment #4)

Great. What does the -s flag do?

-s, --stacktrace Print out the stacktrace for all exceptions.

When your build fails for some reason, you'll get stack trace instead of vague error message.

https://bugzilla.redhat.com/show_bug.cgi?id=1247385

Fedora End Of Life jkurik@fedoraproject.org changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution|--- |EOL Last Closed| |2017-08-08 08:03:03

--- Comment #8 from Fedora End Of Life jkurik@fedoraproject.org --- Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.