On Mon, 18 Nov 2019 21:08:02 -0800, you wrote: >On 11/18/19 7:29 PM, Neal Gompa wrote: >> I can't speak for everyone, but at least my experience was that it was >> functionally impossible to discover how to package Java stuff. In a >> lifetime (and a job) ago, I was much more engaged in the Java >> ecosystem. Back then, I tried to learn how to package and ship Java >> stuff in Fedora. But the documentation was (and still is) incredibly >> poor. I only managed to package one library, and it was not easy for >> me to figure out how to do it. The amount of effort I expended to do >> it put me off to doing more in the Java ecosystem. > >Maybe I misunderstood the earlier comment. I understand that Java can >be difficult to package, but I thought Gerald was saying that using >modules somehow made it easier. I have no idea whether modules make it easier or not. My point was that the Java SIG collapsed long before the modules became an issue, so "rebooting" the Java SIG isn't going to change anything unless those calling for the reboot come up with packagers for the Java ecosystem. And one of the reasons few want to package Java stuff is that because for most of the Java stuff the users prefer to simply install the provided jdk/jre and then download the jar files from upstream, because by using official upstream provided jar files they can get help from upstream with any problems. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
