Talk:Java package guidelines

From ArchWiki
Latest comment: 27 October 2022 by Thaodan in topic Building Java applications from source

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)Reply[reply]

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)Reply[reply]

Building Java applications from source

The edit by User:Diabonas removed the paragraph that building Java applications isn't necessary if not easy to do so. I agree with that but the article should highlight what he mentioned:

he reason for building from source is not just to apply custom build options, but supply chain security, reproducible builds etc. Applications must always be built from source if at all possible

However the article doesn't mention that, please add. I don't think it it not obvious for many that Java applications should be build from source.

--Thaodan (talk) 04:55, 27 October 2022 (UTC)Reply[reply]