Path: csiph.com!weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod
From: Emmanuel Bourg <ebourg@apache.org>
Newsgroups: linux.debian.maint.java
Subject: Re: Packaging questions for css-validator (& webapp/war), servlet-api  2.2...
Date: Mon, 16 Jun 2025 23:20:01 +0200
Message-ID: <KYppf-b39Y-5@gated-at.bofh.it>
References: <KYb2V-aTIh-13@gated-at.bofh.it> <KYb2V-aTIh-11@gated-at.bofh.it> <KYhL3-aYgw-3@gated-at.bofh.it> <KYppf-b39Y-7@gated-at.bofh.it>
Old-Return-Path: <ebourg@apache.org>
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Approved: robomod@news.nic.it
Lines: 37
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:13011

On 16/06/2025 20:32, Fab Stz wrote:

>> You most certainly don't need the Servlet API 2.2, the package should
>> build against libservlet-api-java (Servlet API 4.0) with minor
>> adjustments (if any).
> 
> Actually I did that initially and even tried to "fix it" but that went much
> above my skills and interest. Enough to prefer engaging in making the package
> for api 2.2 and searching its source code (which was not an easy part).
> Actually many functions of servlet >= 2.3 are not implemented in jigsaw. Build
> fails with any servlet-api version >= 2.3. Would anyone try to fix/patch it?
> The package on my salsa repo would be a good starting point since it builds
> fine with the  bin:libjakarta-servletapi-2.2-java package installed, otherwise
> sources (without the debian part) can taken from:
> https://github.com/tenzap/jigsaw (branch with-jdk21).

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?


>>> 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.

Emmanuel Bourg