Talk:Java package guidelines

From ArchWiki
Jump to navigation Jump to search

Java Binary Packages

"You do not need to compile Java applications from source."

What to do if I find a Java package, that is available both as binary and as source package? Are they supposed to co-exist (as packagename-bin and packagename)? Are they supposed to be merged? Is this up to the maintainer?

Concrete case is this and this package, that both provide the JavaFX Scene Builder, as it is developed by Gluon. I decided to notify the maintainer of the first package by leaving a comment, but did not file a merge request.

--Qw3ry (talk) 12:12, 9 December 2016 (UTC)

Jar files (and no other files) [...] in a /usr/share/java/myprogram directory.

I'm assuming this includes .war files as well, seeing as they are basically .jar files. Or?

Necklace (talk) 10:17, 11 September 2019 (UTC)

gradle vs. ./gradlew

Someone just commented on an AUR PKGBUILD that I maintain about Java source upstreams generally prefering for distributions to use bundled gradlew instead of system-wide gradle. After looking into it, it seems like gradlew will download whatever version of gradle is specified, which seems to me like going against the principle of Modernism, since whatever was specified for gradlew is likely not the most recent version. Also, using gradlew will require downloading as part of the makepkg’ing, so package can’t be built offline. OTOH, Simplicity may lean towards using gradlew since that is what upstream gives in their README. Is this something that has been discussed before that I couldn’t find? Is it something that would be worth noting/discussing on this page? —Freso (talk) 23:05, 14 February 2021 (UTC)