Hola Luis,

I know that the remove tomcat9 packages was done on December of 2023 and that this was decided a long time ago. But I think that nobody has stopped to consider that you *cannot simply migrate from Tomcat 9 to 10 *(inserte here

I have. I currently maintain the tomcat9 package externally,
and I have users who use it for their customers so it’s used
in production, with sysvinit instead of systemd, even.

The packages are here: http://www.mirbsd.org/~tg/Debs/dists/bookworm/wtf/Pkgs/tomcat9/

Don’t just install them from there, though, that would not
be secured. Ideally, you’d use the Debian package “extrepo”
to enable the “wtf-lts” repository, then pin it so that only
the packages tomcat9{,-admin,-common,-docs,-examples,-user}
and libtomcat9-{,embed-}java are considered from that repo.

Alternatively, http://www.mirbsd.org/~tg/Debs/debidx.htm
contains links to manual installation instructions, but you
might still want to consider pinning as the repo contains
other packages as well.

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*). I also
haven’t tested installing it together with tomcat10, and I
personally don’t test on bookworm (but others do), only on
bullseye and sometimes buster.

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.

bye,
//mirabilos
--
Infrastrukturexperte • Qvest Digital AG
Am Dickobskreuz 10, D-53121 Bonn • https://www.qvest-digital.com/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 18196 • USt-ID (VAT): DE274355441
Vorstand: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg Vorsitzender Aufsichtsrat: Peter Nöthen

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format.
Hi Luis,

Le 03/05/2024 à 11:54, Luis Panadero Guardeño a écrit :

I know that the remove tomcat9 packages was done on December of 2023
and that this was decided a long time ago. But I think that nobody has stopped to consider that you *cannot simply migrate from Tomcat 9 to
10 *(inserte here meme), because the javax.* to jakarta.* packages
problem. The changes needed to move a web application from javax to
jackarte aren't simple to do. Specially when *3rd party java
libraries, aren't migrated yet to jakarta packages* ( for example
Apache Commons Email ).

You don't have to migrate to the jakarta.* namespace yet, Tomcat 10
supports both javax and jakarta webapps, just install the tomcat-jakartaee-migration package and drop your .war file to the webapps-javaee directory, the classes will be automatically converted, see:

https://tomcat.apache.org/migration-10.html#Specification_APIs

I really hope that someone could reconsider to keep both Tomcat 9 and
Tomcat 10 on Debian 12. If some help it's needed to do this, I could
help (however I don't have idea how to do this).

This won't happen unfortunately, Tomcat is a security intensive package
and we can really maintain efficiently only one version per Debian release.

I choose Debian instead of keeping using Ubuntu server, because the
well know stability of Debian (plus I HATE Canonical weird things and
forcing snap on everything) and I don't expected this kind of changes
inside a stable version.

The javax->jakarta transition is annoying for everyone, but you should
blame Oracle lawyers for this mess, the Debian Java Team is just
following the trend.

Emmanuel Bourg


<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Luis,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 03/05/2024 à 11:54, Luis Panadero
Guardeño a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:[email protected]">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I know that the remove tomcat9 packages was done on December of
2023 and that this was decided a long time ago. But I think that
nobody has stopped to consider that you <b>cannot simply
migrate from Tomcat 9 to 10 </b>(inserte here meme), because
the javax.* to jakarta.* packages problem. The changes needed to
move a web application from javax to jackarte aren't simple to
do. Specially when <b>3rd party java libraries, aren't migrated
yet to jakarta packages</b> ( for example Apache Commons Email
).</p>
</blockquote>
<p>You don't have to migrate to the jakarta.* namespace yet, Tomcat
10 supports both javax and jakarta webapps, just install the
tomcat-jakartaee-migration package and drop your .war file to the
webapps-javaee directory, the classes will be automatically
converted, see:<br>
</p>
<p>   
<a class="moz-txt-link-freetext" href="https://tomcat.apache.org/migration-10.html#Specification_APIs">https://tomcat.apache.org/migration-10.html#Specification_APIs</a><br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:[email protected]">
<p>I really hope that someone could reconsider to keep both Tomcat
9 and Tomcat 10 on Debian 12. If some help it's needed to do
this, I could help (however I don't have idea how to do this).<br>
</p>
</blockquote>
<p>This won't happen unfortunately, Tomcat is a security intensive
package and we can really maintain efficiently only one version
per Debian release.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:[email protected]">
<p> </p>
<p>I choose Debian instead of keeping using Ubuntu server, because
the well know stability of Debian (plus I HATE Canonical weird
things and forcing snap on everything) and I don't expected this
kind of changes inside a stable version.<br>
</p>
</blockquote>
<p>The javax-&gt;jakarta transition is annoying for everyone, but
you should blame Oracle lawyers for this mess, the Debian Java
Team is just following the trend.</p>
<p>Emmanuel Bourg</p>
<p><br>
</p>
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)