On Thu, May 18, 2023, 06:50 Mark Thomas wrote:
>
> 17 May 2023 20:37:01 Christopher Schultz :
>
> > On 5/17/23 04:52, Mark Thomas wrote:
>
> >> Once we switch to using Panama, we are going to have to figure out how
> >> to handle this. My primary concern is new features that depend on API
> >>
17 May 2023 20:37:01 Christopher Schultz :
On 5/17/23 04:52, Mark Thomas wrote:
Once we switch to using Panama, we are going to have to figure out how
to handle this. My primary concern is new features that depend on API
calls only present in newer OpenSSL versions.
The Java components
Mark,
On 5/17/23 04:52, Mark Thomas wrote:
On 16/05/2023 18:12, koteswara Rao Gundapaneni wrote:
To service the SSL tomcat end users are now engaged mostly with HTTPD
SERVER and IBM HTTPD
I don't think that is the case.
Yes, lots of Tomcat instances are behind reverse proxies and yes,
On 16/05/2023 18:12, koteswara Rao Gundapaneni wrote:
To service the SSL tomcat end users are now engaged mostly with HTTPD
SERVER and IBM HTTPD
I don't think that is the case.
Yes, lots of Tomcat instances are behind reverse proxies and yes, lots
of those reverse proxies are
To service the SSL tomcat end users are now engaged mostly with HTTPD
SERVER and IBM HTTPD
If we look at the c,c++,etc API vendors they rarely change thier
Products production at user level - @Mark remarks
On Sat, May 13, 2023 at 1:48 AM Mark Thomas wrote:
> On 12/05/2023 22:24,
On Sat, May 13, 2023 at 10:48 AM Mark Thomas wrote:
>
> On 12/05/2023 22:24, Rémy Maucherat wrote:
> > On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
> >> We would normally make Java 21 the minimum Java version. Given that Java
> >> 21 is still in EA, I don't plan to do that yet.
> >
> >
On 12/05/2023 22:24, Rémy Maucherat wrote:
On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
We would normally make Java 21 the minimum Java version. Given that Java
21 is still in EA, I don't plan to do that yet.
Since the update to Java 21 has now been made and seems to make
everyone
On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
> We would normally make Java 21 the minimum Java version. Given that Java
> 21 is still in EA, I don't plan to do that yet.
Since the update to Java 21 has now been made and seems to make
everyone happy, I would like to discuss Panama.
-
On Thu, Jan 19, 2023 at 10:01 AM Mark Thomas wrote:
>
> Hi all,
>
> As a result of the discussions and reminding myself of various issues I
> intend to proceed as follows:
>
> - Switch the minimum JRE to Java 17 for Tomcat 11. While Jakarta
>EE 11 permits a minimum of Java 21, we will decide
Hi all,
As a result of the discussions and reminding myself of various issues I
intend to proceed as follows:
- Switch the minimum JRE to Java 17 for Tomcat 11. While Jakarta
EE 11 permits a minimum of Java 21, we will decide later whether to
increase the minimum Java version to 21 for
On 12/01/2023 08:35, Rémy Maucherat wrote:
On Wed, Jan 11, 2023 at 10:48 PM Romain Manni-Bucau
wrote:
Guess it was more about default java for linux distro, build is only
reproducible if target --release flag is <= java distro version which will
not be the case for java 21 soon enough
On Wed, Jan 11, 2023 at 10:48 PM Romain Manni-Bucau
wrote:
>
> Guess it was more about default java for linux distro, build is only
> reproducible if target --release flag is <= java distro version which will
> not be the case for java 21 soon enough probably, not really a build issue
> by itself
Guess it was more about default java for linux distro, build is only
reproducible if target --release flag is <= java distro version which will
not be the case for java 21 soon enough probably, not really a build issue
by itself more an ecosystem one - distro consumming sources.
Le mer. 11 janv.
On 11/01/2023 20:15, Michael Osipov wrote:
Even if not, there is another problem with that: When you build with
Java 17, that build cannot be reproduced on Java 11 or 8 because class
file content will be different.
Experience in the Tomcat project says otherwise.
We can already reproduce
On 11/01/2023 14:13, Michael Osipov wrote:
While I cannot comment on Tomcat 11 requirements and Java 21 is
unavoidable I'd like to comment on this because I consider it wrong:
We could switch all branches to Java 17 as the the default build JRE
now as that supports targeting Java 7 onwards.
On 11/01/2023 16:09, Romain Manni-Bucau wrote:
Side question from an user standpoint: does it mean tomcat 11 must not be
used today too since it will abruptally switch its baseline (potentially
against the app baseline)? Isnt it against the 11 releases idea? Thinking
out loud and understanding
Side question from an user standpoint: does it mean tomcat 11 must not be
used today too since it will abruptally switch its baseline (potentially
against the app baseline)? Isnt it against the 11 releases idea? Thinking
out loud and understanding jakarta decision is likely "weird"/inconsistent
Mark,
On 1/11/23 06:23, Mark Thomas wrote:
The Jakarta EE platform group has announced that the minimum Java
version for Jakarta EE 11 will be Java 21. [1]
Given that the Java SecurityManager was deprecated in Java 17 and
planned for removal I intend to remove all references to the
On 11/01/2023 14:13, Michael Osipov wrote:
While I cannot comment on Tomcat 11 requirements and Java 21 is
unavoidable I'd like to comment on this because I consider it wrong:
We could switch all branches to Java 17 as the the default build JRE
now as that supports targeting Java 7 onwards.
While I cannot comment on Tomcat 11 requirements and Java 21 is
unavoidable I'd like to comment on this because I consider it wrong:
We could switch all branches to Java 17 as the the default build JRE now
as that supports targeting Java 7 onwards. That would allow us to easily
use some newer
On Wed, Jan 11, 2023 at 12:44 PM Mark Thomas wrote:
>
> On 11/01/2023 11:38, Rémy Maucherat wrote:
> > On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
>
>
>
> >> The target date for Jakarta EE 11 is Q1 2024. Given that there are no
> >> Java 21 features we want to use in Tomcat 11 right now
On 11/01/2023 11:49, Romain Manni-Bucau wrote:
Hi,
As an user we are adopting Tomcat 11 (even if still "on the edge") with
Java 17 (in particular for some lib/stacks) and the more reactive servlet
6.1 is very interesting so hope it can be made Java 17 compliant until
technically blocked.
On Wed, Jan 11, 2023 at 6:44 AM Mark Thomas wrote:
> On 11/01/2023 11:38, Rémy Maucherat wrote:
> > On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
>
>
>
> Just playing devils advocate for a second, is Java 21 going to be too
> big a leap for the majority of users? Might the Tomcat
Hi,
As an user we are adopting Tomcat 11 (even if still "on the edge") with
Java 17 (in particular for some lib/stacks) and the more reactive servlet
6.1 is very interesting so hope it can be made Java 17 compliant until
technically blocked.
Romain Manni-Bucau
@rmannibucau
On 11/01/2023 11:38, Rémy Maucherat wrote:
On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
The target date for Jakarta EE 11 is Q1 2024. Given that there are no
Java 21 features we want to use in Tomcat 11 right now I suggest we wait
until we need to build Tomcat 11 with Java 21 to
On Wed, Jan 11, 2023 at 12:23 PM Mark Thomas wrote:
>
> Hi all,
>
> The Jakarta EE platform group has announced that the minimum Java
> version for Jakarta EE 11 will be Java 21. [1]
Oh wow, big surprise.
> Given that the Java SecurityManager was deprecated in Java 17 and
> planned for removal
26 matches
Mail list logo
