Path: csiph.com!weretis.net!feeder9.news.weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod From: Emmanuel Bourg Newsgroups: linux.debian.maint.java Subject: Re: Tomcat 9 removed from Debian 12 Date: Sun, 12 May 2024 01:40:01 +0200 Message-ID: References: X-Original-To: Thorsten Glaser X-Mailbox-Line: From debian-java-request@lists.debian.org Sat May 11 23:38:51 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-13.416 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-1.418, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .apache. - helo: .mxout1-ec2-va.apache. - helo-domain: .apache.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 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: 8bit X-Mailing-List: archive/latest/23454 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/dd40b248-5fa8-559e-7a99-b6fe70fb299f@apache.org Approved: robomod@news.nic.it Lines: 24 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-java@lists.debian.org X-Original-Date: Sun, 12 May 2024 01:38:26 +0200 X-Original-Message-ID: X-Original-References: <56d8452f-7eec-1358-6906-dea447cb1196@qvest-digital.com> Xref: csiph.com linux.debian.maint.java:12763 Le 03/05/2024 à 15:46, Thorsten Glaser a écrit : > Full disclosure, while I’m a Debian Developer and team member, > Emmanuel has veto’d the changes to the tomcat9 package in the > past (mostly on the grounds of using adduser… *sigh*). Still shooting in my direction five years later? Will that ever stop? Can't we agree to disagree and move on please? There are other challenges in the Debian Java ecosystem that require our focus and energy. >> because the javax.* to jakarta.* packages problem > > Upstream Tomcat says they can convert that automatically, > but I wouldn’t rely on just that because from experience > I know that upgrading the Tomcat version is always a > breaking change that needs changes to all applications. The Tomcat migration tool is fairly reliable, but if you find specific issues please report them to: https://github.com/apache/tomcat-jakartaee-migration/ Emmanuel Bourg