Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Emmanuel Bourg Newsgroups: linux.debian.maint.java Subject: Re: Packaging questions for css-validator (& webapp/war), servlet-api 2.2... Date: Mon, 16 Jun 2025 15:10:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Mon Jun 16 13:04:20 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-13.199 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-1.201, RCVD_IN_DNSWL_HI=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Greylist: delayed 486 seconds by postgrey-1.36 at bendel; Mon, 16 Jun 2025 13:03:53 UTC Authentication-Results: apache.org; auth=none 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 X-Mailing-List: archive/latest/23735 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/674183b5-d044-7d77-2b62-40c5c4cbe13b@apache.org Approved: robomod@news.nic.it Lines: 49 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 16 Jun 2025 14:55:33 +0200 X-Original-Message-ID: <674183b5-d044-7d77-2b62-40c5c4cbe13b@apache.org> X-Original-References: <3223984.Mh6RI2rZIc.ref@debian> <3223984.Mh6RI2rZIc@debian> Xref: csiph.com linux.debian.maint.java:13009 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). > === |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. > === [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 > 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). Emmanuel Bourg