On Thu, Sep 26, 2019 at 12:19 AM Kevin Kofler kevin.kofler@chello.at wrote:
Emmanuel Seyman wrote:
I'm quite certain that forbidding people to move to module-only would mean that we would not only not have a Java stack in Fedora but also no Java module too.
I think that banning module-only packages would actually get Java back to non-modular-only, since the goal of going module-only is clearly to only do one rather than both. I don't see how maintaining the packages as module- only is in any way less work than maintaining them as non-modular-only. So we need to force the packagers to set the correct priorities for the benefit of the project as a whole.
To make things even more interesting, the non-modular Java stack has almost reached parity with what's available from the shiny module branches, except a handful of packages that require more work than a simple "bump version and build" (for example, the rebase from maven 3.5 to 3.6 is still pending, but I'm planning to work on that soon).
Fabio
Kevin Kofler
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org