https://bugzilla.redhat.com/show_bug.cgi?id=1698504
--- Comment #9 from Adam Williamson awilliam@redhat.com --- "If a default module package trumps the higher NVR of the non-module package, then I don't think your solution to bug 1699852 will work either, right?"
My solution? I haven't solved anything :) I'm just poking bug reports here...
"Isn't the correct solution to bring the module up to date with the F30 version?"
I don't know. It depends what the maven maintainers / module owners are trying to do, I guess. This module stuff is fairly new to me as well, I don't know all the edges of it yet. To be clear, is the problem here that when you build Eclipse, it builds against the non-modular maven? Or are these manually-specified dependencies and you just picked the versions of the dependencies based on the non-modular maven package versions, not realizing that these are no longer the defaults?