On 23/06/2025 20:02, Marco Neumann wrote:
Is it just the war file or the entire web app you want to retire?
This isn't about jena-fuseki-server. That has the newer management
codebase that is in jena-fuseki-main/mod-admin and is the jar file in
apache-jena-fuseki download.
The old codebase jena-fuseki-webapp is a JavaEE webapps (Jakarta).
The application lifecycle is complete different. It is now considered
legacy (maintenance only). A war file is, effectively, sealed (no code
flexibility) and has a different start up architecture, bringing
additional costs to the project.
jena-fuseki-server is has not been using any of jena-fuseki-webapp
jena-fuseki-ui is javascript. That is shared between the war file and
the Fuseki server jar
jena-fuseki-main/mod-admin is the management codebase. It is completely
separate from jena-fuseki-webapp.
Andy
---
Marco Neumann
On Mon, 23 Jun 2025 at 19:58, Andy Seaborne <a...@apache.org> wrote:
Another consideration for change at Jena6.
== Retire the Fuseki WAR file.
That is, the maven modules the code, jena-fuseki-webapp(code), and the
.war packaging (jena-fuseki-war).
jena-fuseki-webapp is already not getting new features.
I don't know of any good way to signal this except to say it in ANN
emails and on the download page https://jena.apache.org/download/.
We can always reverse the decision relatively easily and bring it back
if we keep it in releases for 5.x.
If we don't retire it at Jena 6.0, the next opportunity is a couple of
years away.
Andy
> GH-3201: Remove jena-fuseki-fulljar
> https://github.com/apache/jena/pull/3202
>
> fulljar is a packaging Fuseki/webapp+Jetty as a single jar.
> Now the fuseki-server.jar is no longer the jar in the apache-jena-
> fuseki download (since 5.3.0). There is a PR to remove the one line
> entry for it from the website.
