Le 2020-01-27 10:52, Andrew Haley a écrit :
You would not expect a GCC devroom to be concerned about the problems of all packages written in C and C++, so why would Java be any different?
I would expect a GCC devroom to be concerned about the problems of all packages written in C and C++ once it reached the general failure state that Java exhibits today in Fedora (and, hopefully, before). Problem children happen in all languages and are not a language issue. General failure specific to a language is something else entirely. It does not happen at the individual app level. It happens at the tooling/culture/general priorities level.
The packaging of programs which depend on Java is somewhat outside my remit. Having said that, I am interested to discover why Java packaging in Fedora is particularly dysfunctional.
If you haven’t followed the story there are many people on the list that can explain you in detail what happened (both the people that quit Java packaging side, and the people who’ve been trying to keep the ship from sinking completely since). To keep the story short, the rift between the expectations of Java developers and Java tooling and the needs of the people deploying Java software in Fedora, reached such a level, that people trying to bridge this rift burnt out one after the other and were not replaced. Regards, -- Nicolas Mailhot _______________________________________________ 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
