Fabio Valentini wrote:
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).
Does that include Eclipse, where the packagers recently announced that it would become module-only?
(That said, all the Java projects I work with are set up for NetBeans, so I don't really use Eclipse anyway. I'm just asking for curiosity. Sadly, the NetBeans Fedora package was abandoned long ago, long before Modularity has become a thing, so that one is a wholly different story.)
Kevin Kofler