Arch Linux User Repository

The command listed in https://aur.archlinux.org/packages/nzbhydra2?O=10#comment-887324 doesn't work without further modifications because systemd doesn't expand variables in the Environment directive. As such, starting the service fails because the sh command can't be found. A possible workaround is to hardcode the path, i.e. Environment=PATH="/usr/lib/jvm/java-17-openjdk/bin:/usr/bin"

With the update to version 5, nzbhydra2 now requires java 17, so you'll have to make sure that nzbhydra2 is run with java 17: https://aur.archlinux.org/packages/nzbhydra2?O=10#comment-887324
This is only required for running, the package should build fine in any case.

Furthermore, while nzbhydra2 now also provides binaries for windows and linux (which are apparently built using GraalVM), this package will continue to build the generic jar, as it doesn't seem to be possible to build the binaries with OpenJDK and GraaVM is only available in the AUR.

The command listed in https://aur.archlinux.org/packages/nzbhydra2?O=10#comment-887324 doesn't work without further modifications because systemd doesn't expand variables in the Environment directive. As such, starting the service fails because the sh command can't be found. A possible workaround is to hardcode the path, i.e. Environment=PATH="/usr/lib/jvm/java-17-openjdk/bin:/usr/bin"

With the update to version 5, nzbhydra2 now requires java 17, so you'll have to make sure that nzbhydra2 is run with java 17: https://aur.archlinux.org/packages/nzbhydra2?O=10#comment-887324
This is only required for running, the package should build fine in any case.

Furthermore, while nzbhydra2 now also provides binaries for windows and linux (which are apparently built using GraalVM), this package will continue to build the generic jar, as it doesn't seem to be possible to build the binaries with OpenJDK and GraaVM is only available in the AUR.

@jkhsjdhjs the AUR maintainers of the earth are great, but you exceed them all.

@hicklemon I was able to reproduce your issue by setting JAVA_HOME to an arbitrary path. Please either set JAVA_HOME correctly (export JAVA_HOME=/usr/lib/jvm/<jdk-of-your-choice>) or unset it (unset JAVA_HOME).

EDIT: I changed the PKGBUILD to require OpenJDK 11 for building and always build with OpenJDK 11 no matter what the default environment set with archlinux-java is.
You no longer have to change the default environment with archlinux-java to build this package!
I did it by exporting JAVA_HOME in the build() and check() functions. They're doing it for official repository packages as well (e.g. tomcat8), so it should be fine.

i decided to update today, and i dunno why, but this decided to blow up! :) i was on java (17) NO, i was on 19!!! ... and everything was perfectly fine before. upon reading this thread, i've removed java 17 and installed java 11, and done the thing with archlinux-java as root as is tradition and it's torched.

==> Starting build()...
The JAVA_HOME environment variable is not defined correctly,
this environment variable is needed to run this program.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: nzbhydra2

JAVA_HOME... story of my life.

I'm not sure why the github-release-plugin and other stuff like discordbot and githubbot were even built. It's not like they're required for nzbhydra, so I added a patch to skip building them.

Unfortunately at least mapping also can't be built with OpenJDK 17, so older JDKs are still required.

I also added a check for unsupported JDKs to the build() function of the PKGBUILD.

@sovanyio Are you sure that OpenJDK 8 or 11 are actually being used? Because that is precisely the error I got when trying to build with OpenJDK 17. Try

# archlinux-java set java-11-openjdk

Build is failing in the maven github-release-plugin on openjdk 8 and 11 for me

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project github-release-plugin: Fatal error compiling: java.lang.ExceptionInInitializerError: Unable to make field private com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors com.sun.tools.javac.processing.JavacProcessingEnvironment.discoveredProcs accessible: module jdk.compiler does not "opens com.sun.tools.javac.processing" to unnamed module @6c07ad6b -> [Help 1]

Funny, I went looking for your email in your profile because doing this via comments felt silly, but it was hidden! I just found your email in my spam folder and unmarked it, so thats fine. We could also do nzbhydra2's discord. I pay very little attention to my irc client, sadly. Probably you were a victim of sending me a message that got ignored when I rebooted. :P

@fryfrog I never built .NET applications before, but I also never built Java with maven before this package. I'll give it a try :D

BTW: Before pushing the changes to this package I also sent you a mail and tried to contact you via IRC, since I wanted to discuss them with you. Is there any way I can contact you aside from AUR comments?