Github user stain commented on the issue:
https://github.com/apache/jena/pull/50
I have updated https://hub.docker.com/r/stain/jena/ and
https://hub.docker.com/r/stain/jena-fuseki/ to the latest releases (3.2.0,
2.5.0).
It's now based on `java:8-jre-alpine` base image so it should automatically
updated with a newer java arrives.
I am a bit hampered trying to contribute to this as I am not a Jena
committer and don't want to step on toes; after all, releasing Jena is the job
of the PMC.
I think this pull request is moot, it is very difficult to test it with the
Docker build as part of the source build, as basically you will require a new
compilation of the whole thing inside `Dockerfile`, or you would have to use a
Maven plugin to build the Docker image (which would then require Docker
installed).
Jena already have a massive git repository which can take considerable time
& disk to build, and I don't think it's right to add more to it.
I think Jena and Fuseki should become two official images under the `_`
namespace in Docker H
hub - and then there should be a mini-git repository "jena-docker" -
similar to [my jena-docker](https://github.com/stain/jena-docker) - but hosted
under `apache/`, which could then be referenced from
https://github.com/docker-library/official-images.
That image will then simply pull the latest release from `dist.apache.org`
and one only need to update version number and sha1 on any new release. As the
binary is the same (just unpacked), no additional PMC release vote should be
needed.
Alternatively there could be a `jena` repository under
https://github.com/docker-library/ managed by some PMC members.
Obviously as such an image should be "official" I am unable to try to work
on it in that way, as I am neither a committer nor on the PMC.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
