Docker Image for Eclipse GlassFish
Summary
OmniFish agreed with migration of its three GitHub repositories under the Eclipse GlassFish project. However I don't have such permissions and also I am not sure what else has to be done for that, but I am ready to cooperate.
Current State and Problems to Solve
- OmniFish invested time and effort to a creation of the Docker Image for Eclipse GlassFish and made it publicly available under https://hub.docker.com/r/omnifish/glassfish .
- OmniFish created a PR with the intention to adopt abandoned official GlassFish dockerhub repository, so GlassFish would have an official docker image again. Our intentions were good, however in a discussion we were warned that the PR might be controversial against Eclipse's guidelines.
- So we agreed to move our repositories to the Eclipse GlassFish project and update the PR.
- Until DockerHub team merges our PR, GlassFish will release docker images under the GitHub packages.
- Jakarta EE Starter project then can use these images as Eclipse's official docker images.
Repositories
Note that those docker.io forks are not under Eclipse.
The original PR to be updated (by me) to use new Eclipse repositories: https://github.com/docker-library/official-images/pull/14107
Questions
- Who is responsible to negotiate the correct solution with us?
- Should those two forked docker.io repositories (official-images and docs) move to Eclipse too? Seems there is a good reason why Jetty did not do that. Jetty Project mentions IP Policy as a reason.
Draft of a Plan
- Fork https://github.com/OmniFish-EE/docker-library-glassfish to https://github.com/eclipse-ee4j/docker-library-glassfish with permissions for glassfish committers.
- Configure Jenkins job to automate the build of the docker image (one parameter - GlassFish version):
mvn clean verify -Dglassfish.version=7.0.4
- The https://github.com/OmniFish-EE/docker-library-official-images and https://github.com/OmniFish-EE/docker-library-docs - see question 2. If it would be a problem, they can remain under OmniFish and OmniFish can continue with the PR to DockerHub. Basically it would be the same model as for Jetty.
Known Limitations
- Overwriting packages will not be possible this way. Until now it was.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Edited by David Matějček