Re: Packaging questions for css-validator (& webapp/war), servlet-api 2.2...

Fab Stz <[email protected]> Tue, 17 Jun 2025 07:33:54 +0200
Newsgroups gmane.linux.debian.devel.java
Message-ID <8819347.EvYhyI6sBW@debian>
Le lundi 16 juin 2025 23:03:25 CEST, vous avez écrit :
> I just realized that Jigsaw is actually a web server, so that's not
> surprising if it doesn't build with the Servlet API 4.0.
> 
> But this raises another question: why a 20 year old unmaintained web
> server is necessary? Is it possible to do without it?

I don't know exactly. Digging into the internals of jigsaw to know why would 
be too time-consuming. I have 2 guesses:
- css-validator can be installed into tomcat but also jigsaw (see https://
jigsaw.w3.org/css-validator/DOWNLOAD.html )
- css-validator requires package "org.w3c.www.http" (~60 classes) and some of 
its dependencies that are shipped in jigsaw.

> >>> How would you ship the **war** or **webapp**?
> >> 
> >> If vnu doesn't require the webapp, do not package it. Let's keep things
> >> simple (and fun).
> > 
> > Now that it's done, can I leave it that way instead of just throwing all
> > the work away?
> > It can actually have some interest to deploy the war/webapp on the server
> > (jetty/tomcat) that's why I packaged it.
> 
> It's also about avoiding extra work in the future for maintaining a
> package that may not be used.

I find it useful to ship also the webapp. Without it, we only have the command 
line interface and I don't know if it is feature-equivalent. All the html 
files of the webapp are not shipped otherwise. We could also drop the package 
in future if it is source of problems or maintenance burden?

Regards
Fab