[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



On 17/06/2025 07:33, Fab Stz wrote:

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.

I got a look and I confirm it's possible to build css-validator without jigsaw, by just importing a few classes:

https://github.com/w3c/css-validator/pull/449


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?

But why would one want to install a CSS validation service when there is already one hosted by the W3C? I see the value in the command line tool, but not much in the web service. But if you are ready to maintain it in the next 10 years, why not.

Emmanuel Bourg


Reply to: