Am 12.08.2018 um 00:52 schrieb Emmanuel Bourg:
[...]
>> I can start packaging
>> libservlet4.0-java (I would name source and binary package the same). Is
>> it this one?
>>
>> https://github.com/javaee/servlet-spec/releases/tag/4.0.1
>
> Yes that's this one, thank you for jumping in but I've alre
On Sun, 12 Aug 2018, Emmanuel Bourg wrote:
> (servlet-api), and spin-off a versionned packages only if required due
Either way (versioned or not), wouldn’t
libservlet-api-java
be a less conflicting, more in line with the common
practice at Debian, package name? (Consider Perl stuff.)
J
Le 11/08/2018 à 09:19, Markus Koschany a écrit :
> That is a very good idea. I also think that it makes sense to decouple
> the Servlet API from src:tomcat{7,8,9}
>
> +1
>
> +1
Thank you for the feedback!
> As long as we don't have to change reverse-dependencies and everything
> is just a dro
Hi!
Am 06.08.2018 um 12:47 schrieb Emmanuel Bourg:
> Hi all,
>
> I'm starting to plan the packaging of Tomcat 9 which should be the
> version of Tomcat shipped with Buster. Before doing that I'd like to
> rethink how the Servlet/JSP API are packaged in Debian.
[...]
That is a very good idea. I
Le 06/08/2018 à 12:47, Emmanuel Bourg a écrit :
> Historically the
> tomcat packages have been the source of the libservlet-java packages:
> * src:tomcat6 had libservlet2.5-java containing the Servlet 2.5,
> JSP 2.1 and EL 2.1 APIs
> * src:tomcat7 has libservlet3.0-java containing the Servlet 3.
Hello Emanual,
I agree the servlet-api should live/be built by their own packages.
>From a development point of view they are part of Java EE/Jakarta EE and
tomcat consumes them.
Having multiple versions of the API in Debian also makes.
Regards,
Eugen
On 06.08.2018 13:47, Emmanuel Bourg wrot
6 matches
Mail list logo
