Arch Linux User Repository

I've added a warning and instructions in case the build fails.

It's not possible (or at least feasible) to set JAVA_HOME during the build process, as there might be a lot of compatible JDKs. jdk8-openjdk and graal-bin for example work, but there might be more. I don't want to force the user to install e.g. jdk8-openjdk if she already has another compatible JDK installed.

1. I agree and that would introduce an overhead of migration/patching.
2. It's doable but I wouldnt do it neither. It just change the concept of creating arch package. Meybe one day the whole community will be willing to go that way.
3. I agree gradlew is enough. Regarding the second part. I would add jdk8(-11?) as a build dependency and set JAVA_HOME variable as a part of gradlew command. There is a java environment restriction but it does not install any jdk for a building time.

I partially agree that devs can handle this issue but on the other hand creating a package should be fully automated.

1. gradle 6 is not available in the archlinux repos, using it would be a non-standard build process anyway
2. i won't add docker as a makedep.
3. there's no need for another gradle version, we can use the supplied gradlew, but that only works with jdk8(?), but we can't properly set JAVA_HOME during build process because we don't know which supporting jdk is installed on the users machine

Neverlesess I think that users of this package are seasoned java developers and can get around this. Just set JAVA_HOME to a jdk supported by gradle 4.4 for the build process (e.g. jdk8).

1. gradle6 is already released
2. you may use gradle:4.4-jdk8 docker image and run something like that: docker run --rm -u gradle -v "$PWD":/home/gradle/project -w /home/gradle/project gradle gradle <gradle-task> but that changes the concept of build dependencies for Arch Linux packages
3. What's missing in Arch is ability to easily change Gradle for build time as you may do for java (using command: archlinux-java). I already asked the maintainer of gradle4 to remove conflict flag for gradle(5) package. Thus these two can be installed together. I wouldn't have given up this package if I have had more time.

Currently the build uses gradlew which in this project is quite old (4.6) and doesn't even work with jdk11. We could use a newer gradle as makedep but this wouldn't work with jdk13 as well, as jdk13 support will land in gradle 6 and that's not released yet (docker won't help either). For the time being I'll stick to the original build process and add a makedep for java-environment<11. The resulting executable seems to run fine on jdk13 though.

I'm sorry guys but recently I didn't have time to update. I discovered an issue, that from my point of view should be addressed. The project is based on gradle4 however gradle in this version does not support jdk13. I think that we can't be bound to jdk <8,11). We may always use docker image for building but I'm not sure if that's not an overhead. Please suggest a gentle solution for that. I'm ready to disown package.

You can file a request to disown the package.

This has been out of date for more than 2 months. Don't want to push you, but should I take over?

This has been out of date for more than 2 months. Don't want to push you, but should I take over?

I don't really care. You can have the entire package. I don't really need this anymore.