In the maven module, glassfish-el is filtered  but not glassfish-el-api subpackage:
Because Eclipse requires both glassfish-el and glassfish-el-api, but glassfish-el is not available from maven, I tried to include the package in the Eclipse module, but that causes bug 1759176
And obviously I can't recommend users disable all their Java modules to install dangerously out-of-date ursine packages.
My ideal solution is to make eclipse:latest a default module stream so that users get all the correct packages from the modules, but apparently default modules are not allowed to ship duplicate packages.
Please consider removing glassfish-el from the filter list of maven:3.5 -- this will enable me to drop glassfish-el from the Eclipse module, and that should allow me to make Eclipse a default module, which should fix the upgrade path from ursine to modular Eclipse.
BTW The dangerously out-of-date ursine packages seem to be at the same version as the modular ones, at least when it comes to glassfish-el.
Maven 3.6 already dropped glassfish-el, so I am going to backport this change to 3.5 stream too.
But I'm blocked by a few external things:
- javapackages module branches are marked as EOL in PDC, so I can't commit to them - I have asked Release Engineering to update component branch SLA in ticket https://pagure.io/releng/issue/8877
- I don't have commit ACL on some dist-git repos - I have asked maintainer to grant me commit ACL in ticket https://pagure.io/stewardship-sig/issue/53
maven 3.5 stream branch is marked as inactive in PDC, I will need to request its re-activation.
Created attachment 1623730 [details]
(In reply to Mikolaj Izdebski from comment #3)
> maven 3.5 stream branch is marked as inactive in PDC, I will need to request
> its re-activation.
The releng bug was resolved so I applied the patch. However I could not attempt a build:
$ fedpkg module-build
Submitting the module build...
Could not execute module_build: The build failed with:
None of the base module (platform or bootstrap) streams in the buildrequires section could be found
I assume this is because F28 it no longer a valid platform on which to build since its retirement.
maven:3.5 module was switched to build-depend on platform:f29
Resolution of this issue is blocked by releng ticket: https://pagure.io/releng/issue/8909
Module build #6921 is complete.
Bodhi updates are blocked on infra issue https://pagure.io/fedora-infrastructure/issue/8336
Pending Bodhi updates:
Pushing update to stable is blocked on Bodhi issue https://github.com/fedora-infra/bodhi/issues/3708
maven-3.5-2920191030094746.868ae023 has been pushed to the Fedora 31 Modular stable repository. If problems still persist, please make note of it in this bug report.
maven-3.5-2920191030094641.868ae023 has been pushed to the Fedora 29 Modular stable repository. If problems still persist, please make note of it in this bug report.
maven-3.5-2920191030094717.868ae023 has been pushed to the Fedora 30 Modular stable repository. If problems still persist, please make note of it in this bug report.