Re: Packaging questions for css-validator (& webapp/war), servlet-api 2.2...
Hello,
Thanks for the reply.
Le lundi 16 juin 2025 14:55:33 CEST, vous avez écrit :
> On 16/06/2025 07:40, Fab Stz wrote:
> > Questions:
> >
> > === [servlet api 2.2] src:jakarta-servletapi-2.2 ? ===
>
> 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).
> > === |jigsaw] src:jigsaw ===
> >
> > Package produces 3 jars. One of them is used in other packages (and
> > published on maven), others are internal (and not on maven). Should I
> > have 1 binary package for each like this (or just put all 3 in the 1st
> > one like I'm doing presently)?
>
> If jigadmin and jigedit aren't necessary, don't package them. Also don't
> bother packaging the javadoc.
They are needed to administer jigsaw, but not for the library.
> > === [css-validator] src:css-validator ===
> >
> > Upstream permits to build jar and war.
> >
> > It can be invoked by command line, and is also a webapp (usable in jigsaw,
> > but also tomcat9/jetty9 (support for the **javax.servlet** package/api is
> > required).
> >
> > For the **jar**, given that on the one hand it is an application, and on
> > the other hand that it is used as a dependency for vnu, should it go to
> > /usr/ share/java/css-validator.jar or to
> > /usr/share/css-validator/css-validator.jar (which is my present choice)?
> > Shipped in bin:libcss-validator-java or bin:css- validator (present
> > choice)?
>
> Typical packaging for a command line tool that can be used as a library:
> - bin:libfoo-java contains the jar in /usr/share/java (and maybe the
> Maven artifacts in /usr/share/maven-repo)
> - bin:foo depends on libfoo-java and a Java runtime, contains scripts
> and related files in /usr/share/foo
Ok, I'll adjust accordingly.
> > 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.
Regards
Fab
Reply to: