On 06/05/2025 11:09, Rémy Maucherat wrote:
On Tue, May 6, 2025 at 9:48 AM Mark Thomas wrote:
Hi all,
I am currently working on a couple of platform specific test failures.
I have fixed one of these (the JSP compilation bug) but still have
another to fix (TestGenerator fails on Windows).
On Tue, May 6, 2025 at 9:48 AM Mark Thomas wrote:
>
> Hi all,
>
> I am currently working on a couple of platform specific test failures. I
> also want to try and fix the issue described in "Content type unknown
> after upgrading Tomcat 10.1.39 => 10.1.40" on the users list.
I had missed it. It se
Hi all,
I am currently working on a couple of platform specific test failures. I
also want to try and fix the issue described in "Content type unknown
after upgrading Tomcat 10.1.39 => 10.1.40" on the users list.
I'm hopeful that I'll be able to tag 11.0.x later today or early tomorrow.
Mark
both language AND
country for official releases."
c50e7844dc is described below
commit c50e7844dc8dadd379b80a039ad06eaa52cba447
Author: Christopher Schultz
AuthorDate: Wed Apr 9 09:49:14 2025 -0400
Revert "Javadoc locale should have both language AND country for off
On 01/04/2025 09:31, Emmanuel Bourg wrote:
On 01/04/2025 10:06, Mark Thomas wrote:
Did you figure out the file handler issue with Jsign 7.1?
The issue was with 7.0 - we were seeing the "Unsupported file" error
with Ant.
I don't recall any issues with 7.1. I'm currently running my tests so
On 01/04/2025 10:06, Mark Thomas wrote:
Did you figure out the file handler issue with Jsign 7.1?
The issue was with 7.0 - we were seeing the "Unsupported file" error
with Ant.
I don't recall any issues with 7.1. I'm currently running my tests so I
should be in a position to tag (and test
On 31/03/2025 22:39, Emmanuel Bourg wrote:
Hi Mark,
On 31/03/2025 16:51, Mark Thomas wrote:
I have a couple of tasks to get done (update JSign, update i18n
strings) and then I should be ready to tag 11.0.6. I am currently
hoping to be able to do that tomorrow.
Did you figure out the file ha
Hi Mark,
On 31/03/2025 16:51, Mark Thomas wrote:
I have a couple of tasks to get done (update JSign, update i18n strings)
and then I should be ready to tag 11.0.6. I am currently hoping to be
able to do that tomorrow.
Did you figure out the file handler issue with Jsign 7.1?
Emmanuel Bourg
Mark,
On 3/31/25 10:51 AM, Mark Thomas wrote:
I have a couple of tasks to get done (update JSign, update i18n strings)
and then I should be ready to tag 11.0.6. I am currently hoping to be
able to do that tomorrow.
👍
I'm ready for 10.1.x when you are satisfied with 11.
-chris
adoroszlai commented on PR #2:
URL: https://github.com/apache/tomcat-tck/pull/2#issuecomment-2766744340
Thanks @markt-asf for merging this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the spe
releases for asf-snapshots
c2e348c is described below
commit c2e348c496ff4b5aac4b6f8d4148adfd56f9b7df
Author: Doroszlai, Attila
AuthorDate: Sat Dec 14 15:00:42 2024 +0100
prefer central repo, disable releases for asf-snapshots
---
pom.xml | 11 +++
1 file changed, 7 insertions(+), 4
markt-asf merged PR #2:
URL: https://github.com/apache/tomcat-tck/pull/2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.o
Hi all,
I have a couple of tasks to get done (update JSign, update i18n strings)
and then I should be ready to tag 11.0.6. I am currently hoping to be
able to do that tomorrow.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...
On Wed, Feb 26, 2025 at 1:32 PM Dimitris Soumis wrote:
> Hi all,
>
> I was verifying the signature for the Tomcat 10.1.36 source tarball and
> noticed that the RSA key used to sign it (
> 3262A061C42FC4C7BBB5C25C1CF0293FA53CA458) is not present in the KEYS
> files. That is the case for 10.1.35 to
Hi all,
I was verifying the signature for the Tomcat 10.1.36 source tarball and
noticed that the RSA key used to sign it (
3262A061C42FC4C7BBB5C25C1CF0293FA53CA458) is not present in the KEYS files.
That is the case for 10.1.35 too.
Kind regards,
Dimitris
language AND country for
official releases.
9412c022fe is described below
commit 9412c022fe1cd4736f1e8e8147f744d42cfd487d
Author: Christopher Schultz
AuthorDate: Wed Feb 12 08:23:42 2025 -0500
Javadoc locale should have both language AND country for official releases.
---
build.properties.default
adoroszlai commented on PR #2:
URL: https://github.com/apache/tomcat-tck/pull/2#issuecomment-2549076448
@markt-asf could you please help review this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
/maven2/, default, releases)
[INFO]First introduced on root
[INFO] * asf-snapshots
(https://repository.apache.org/content/groups/snapshots/, default, snapshots)
[INFO]First introduced on root
[INFO] * asf-staging
(https://repository.apache.org/content/groups/staging/, default
See BZ 69320. I've reproduced the issue on 10.1.x. Haven't tested other
versions yet or started to look for a root cause. That is next.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands,
On Tue, Sep 3, 2024 at 4:00 PM Mark Thomas wrote:
>
> Hi all,
>
> I'm just wrapping up the fix for BZ 69302. Once that is committed, I
> expect to tag 11.0.0-M25.
>
> I also think we need to start thinking about declaring 11.0.x stable.
> The specs are implemented, the TCKs are passing, 11.0.x is
Hi all,
I'm just wrapping up the fix for BZ 69302. Once that is committed, I
expect to tag 11.0.0-M25.
I also think we need to start thinking about declaring 11.0.x stable.
The specs are implemented, the TCKs are passing, 11.0.x is pretty close
to 10.1.x.
A thought that has been forming is
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/main by this push:
new d801063447 Assume point releases for all specs as a
Hi all,
I have a couple of things to finish off (testing Tomcat Native 1.3.1,
back-porting the translations) but hope to be in a position to tag
11.0.x later today.
The TCK run seems to be failing consistently for Java 17 and Windows. I
need to look into why. I haven't been able to reproduce
e are happy with it.
-chris
On 11/06/2024 21:46, Christopher Schultz wrote:
Mark,
On 6/10/24 04:06, Mark Thomas wrote:
A bunch of minor issues built up in my TODO list while I was at
Community over Code and the Tomcat security day. I'd like to clear
these before I tag the June releas
wrote:
> > Mark,
> >
> > On 6/10/24 04:06, Mark Thomas wrote:
> >> A bunch of minor issues built up in my TODO list while I was at
> >> Community over Code and the Tomcat security day. I'd like to clear
> >> these before I tag the June relea
On 11/06/2024 21:46, Christopher Schultz wrote:
Mark,
On 6/10/24 04:06, Mark Thomas wrote:
A bunch of minor issues built up in my TODO list while I was at
Community over Code and the Tomcat security day. I'd like to clear
these before I tag the June releases.
+1
In related news, t
Mark,
On 6/10/24 04:06, Mark Thomas wrote:
A bunch of minor issues built up in my TODO list while I was at
Community over Code and the Tomcat security day. I'd like to clear these
before I tag the June releases.
+1
In related news, the release ballots for Servlet and Pages have
comp
Hi all,
A bunch of minor issues built up in my TODO list while I was at
Community over Code and the Tomcat security day. I'd like to clear these
before I tag the June releases.
In related news, the release ballots for Servlet and Pages have
completed successfully. There is some admin
On Thu, May 2, 2024 at 7:26 PM Mark Thomas wrote:
>
> Hi all,
>
> Things are looking good for the May releases. I have a few things to
> back-port to 10.1.x and 9.0.x and then I'll start running my pre-release
> tests. Providing everything passes (and CI runs suggest they
Hi all,
Things are looking good for the May releases. I have a few things to
back-port to 10.1.x and 9.0.x and then I'll start running my pre-release
tests. Providing everything passes (and CI runs suggest they will) I'll
tag 11.0.x - probably some time tomorr
On Sun, Apr 7, 2024 at 9:33 PM Mark Thomas wrote:
>
> On 07/04/2024 17:44, Rémy Maucherat wrote:
> > On Sat, Apr 6, 2024 at 2:21 PM Mark Thomas wrote:
> >>
> >> 5 Apr 2024 14:18:49 Rémy Maucherat :
> >>
> >>> On Fri, Apr 5, 2024 at 2:02 PM Mark Thomas wrote:
>
> Hi all,
>
> J
On 07/04/2024 17:44, Rémy Maucherat wrote:
On Sat, Apr 6, 2024 at 2:21 PM Mark Thomas wrote:
5 Apr 2024 14:18:49 Rémy Maucherat :
On Fri, Apr 5, 2024 at 2:02 PM Mark Thomas wrote:
Hi all,
Just a heads up that I have a lot on my plate at the moment and the
April
tag for 11.0.x is unlikely
On Sat, Apr 6, 2024 at 2:21 PM Mark Thomas wrote:
>
> 5 Apr 2024 14:18:49 Rémy Maucherat :
>
> > On Fri, Apr 5, 2024 at 2:02 PM Mark Thomas wrote:
> >>
> >> Hi all,
> >>
> >> Just a heads up that I have a lot on my plate at the moment and the
> >> April
> >> tag for 11.0.x is unlikely to happen f
5 Apr 2024 14:18:49 Rémy Maucherat :
On Fri, Apr 5, 2024 at 2:02 PM Mark Thomas wrote:
Hi all,
Just a heads up that I have a lot on my plate at the moment and the
April
tag for 11.0.x is unlikely to happen for a couple of weeks.
There are changes I'd like to see in a release but I don't t
On Fri, Apr 5, 2024 at 2:02 PM Mark Thomas wrote:
>
> Hi all,
>
> Just a heads up that I have a lot on my plate at the moment and the April
> tag for 11.0.x is unlikely to happen for a couple of weeks.
>
> There are changes I'd like to see in a release but I don't think there is
> anything urgent.
Hi all,
Just a heads up that I have a lot on my plate at the moment and the April
tag for 11.0.x is unlikely to happen for a couple of weeks.
There are changes I'd like to see in a release but I don't think there is
anything urgent.
Mark
Change default build-age warning from (disabled) to 180 days for final
8.5.x releases.
---
.../apache/catalina/security/.SecurityListener.java.swp | Bin 20480 -> 0 bytes
java/org/apache/catalina/security/SecurityListener.java | 2 +-
webapps/docs/config/listeners.xml |
always change our minds and release
again if there is something vital.
Following up on this, I think the bug fix for BZ 68495 does make it
worth doing a set of releases this month.
The dependencies are up to date, I've just updated the translations and
we don't have any open bugs at the mome
should release 8.5.100 in March, if only to meet our own goal
> > of "ending support at the end of March". There isn't likely to be
> > anything so important that it needs to be added after that.
> >
> > We made a few exceptions for Tomcats 6, 7, and 8.0 for se
s
something vital.
Following up on this, I think the bug fix for BZ 68495 does make it
worth doing a set of releases this month.
The dependencies are up to date, I've just updated the translations and
we don't have any open bugs at the moment.
There is the sproadic test failure i
Mark,
On 2/27/24 06:20, Mark Thomas wrote:
On 27/02/2024 10:57, Rémy Maucherat wrote:
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
All,
When I look at the current change logs there isn't much there to justify
a March release. There are a couple of open bugs of which one looks
likely
On Tue, Feb 27, 2024 at 12:20 PM Mark Thomas wrote:
>
> On 27/02/2024 10:57, Rémy Maucherat wrote:
> > On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
> >>
> >> All,
> >>
> >> When I look at the current change logs there isn't much there to justify
> >> a March release. There are a couple of
On 27/02/2024 10:57, Rémy Maucherat wrote:
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
All,
When I look at the current change logs there isn't much there to justify
a March release. There are a couple of open bugs of which one looks
likely that there is an actual issue to be fixed.
T
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
>
> All,
>
> When I look at the current change logs there isn't much there to justify
> a March release. There are a couple of open bugs of which one looks
> likely that there is an actual issue to be fixed.
>
> That said, I'm unlikely to be in a
All,
When I look at the current change logs there isn't much there to justify
a March release. There are a couple of open bugs of which one looks
likely that there is an actual issue to be fixed.
That said, I'm unlikely to be in a position to tag 11.0.x until w/c 11
March. The change log may
Mark,
On 2/1/24 18:07, Mark Thomas wrote:
On 01/02/2024 23:45, Christopher Schultz wrote:
All,
Friday seems like a good time to roll a release and call for a vote.
Does anyone want to fit anything in before this round of releases?
Yes. The update to the migration tool.
Okay. Does the
On 01/02/2024 23:45, Christopher Schultz wrote:
All,
Friday seems like a good time to roll a release and call for a vote.
Does anyone want to fit anything in before this round of releases?
Yes. The update to the migration tool.
We might want to think about a Tomcat Native release to pick up
All,
Friday seems like a good time to roll a release and call for a vote.
Does anyone want to fit anything in before this round of releases?
-chris
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional
DanielThomas commented on issue #48:
URL:
https://github.com/apache/tomcat-jakartaee-migration/issues/48#issuecomment-1913758414
Some improvements got made to this mitigation in later JDK releases, due to
false positives in the detection, so I think this has been addressed upstream
> >> short but there is a fix for the regression in parsing keys/certs
> >> generated by older OpenSSL versions.
> >>
> >> I was planning on implementing a fix for BZ 68348 [1] and could tag
> >> after that if there is general agreement to do a releas
implementing a fix for BZ 68348 [1] and could tag
after that if there is general agreement to do a release round this
month.
I'm perfectly happy to do a set of releases.
I wouldn't merge my CSRF PR until I've added some unit tests and made a
few other changes, so there is no need t
after that if there is general agreement to do a release round this month.
I'm perfectly happy to do a set of releases.
I wouldn't merge my CSRF PR until I've added some unit tests and made a
few other changes, so there is no need to wait for that.
Fixing the PEM parsing is wo
On Tue, Jan 2, 2024 at 12:30 PM Mark Thomas wrote:
>
> Hi all,
>
> What do we think about a January release? The changelog is fairly short
> but there is a fix for the regression in parsing keys/certs generated by
> older OpenSSL versions.
Yes, I was looking at the changelog earlier (hence updati
Hi all,
What do we think about a January release? The changelog is fairly short
but there is a fix for the regression in parsing keys/certs generated by
older OpenSSL versions.
I was planning on implementing a fix for BZ 68348 [1] and could tag
after that if there is general agreement to do
On 2023/09/26 10:47:34 Mark Thomas wrote:
> Hi all,
>
> With OpenSSL 1.1.1 reaching EOL and there being a low severity issue in
> the OpenSSL versions used in the Windows binaries for the last releases,
> I'd like to propose a new set of Tomcat Native releases that:
>
Hi all,
With OpenSSL 1.1.1 reaching EOL and there being a low severity issue in
the OpenSSL versions used in the Windows binaries for the last releases,
I'd like to propose a new set of Tomcat Native releases that:
- include the fix for BZ 67061
- include binaries built with the l
aooohan merged PR #241:
URL: https://github.com/apache/tomcat/pull/241
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
testAllIdle releases them
f1e571a9ef is described below
commit f1e571a9ef3026e594c1fbe0fbba3b550f5a02ed
Author: Arun Chaitanya Miriappalli
AuthorDate: Fri Feb 14 15:39:14 2020 +0800
Increment ReleaseIdle Counter when testAllIdle releases them
---
.../src/main/java/org/apache/tomcat/jdbc/pool
aooohan commented on PR #241:
URL: https://github.com/apache/tomcat/pull/241#issuecomment-1665089645
Ok, you are right. It does seem to have been overlooked.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 1.2.x
in repository https://gitbox.apache.org/repos/asf/tomcat-native.git
The following commit(s) were added to refs/heads/1.2.x by this push:
new 7491fb391 Correct branch for 1.2.x releases
On Mon, Jul 31, 2023 at 10:54 AM Mark Thomas wrote:
>
> There are OpenSSL releases due tomorrow with security fixes. Given the
> timing, I'm going to delay the Tomcat Native tags to pick up those releases.
Makes sense.
Rémy
> Mark
>
>
> On 31/07/2023 09:12, Mar
There are OpenSSL releases due tomorrow with security fixes. Given the
timing, I'm going to delay the Tomcat Native tags to pick up those releases.
Mark
On 31/07/2023 09:12, Mark Thomas wrote:
Hi all,
I have been working on BZ 9 [1] and have confirmed a small memory
leak when
Hi all,
I have been working on BZ 9 [1] and have confirmed a small memory
leak when using Tomcat Native. I have a fix and will be committing it
shortly. I plan to start the release process for Tomcat Native 1.2.x and
2.0.x shortly afterwards. I'd like to delay the August Tomcat rel
On Sun, Jul 9, 2023 at 12:04 PM Mark Thomas wrote:
>
>
> 7 Jul 2023 15:52:30 Christopher Schultz :
>
> > All,
> >
> > I will be on holiday around the time I would usually do the monthly
> > releases for August, for 10.1.12 and 8.5.92.
> >
> > I&#x
7 Jul 2023 15:52:30 Christopher Schultz :
All,
I will be on holiday around the time I would usually do the monthly
releases for August, for 10.1.12 and 8.5.92.
I'm happy to do those releases when I return, but if someone thinks
that the August releases on these branches is important
All,
I will be on holiday around the time I would usually do the monthly
releases for August, for 10.1.12 and 8.5.92.
I'm happy to do those releases when I return, but if someone thinks that
the August releases on these branches is important need to be "on time"
then I'
https://bz.apache.org/bugzilla/show_bug.cgi?id=60918
--- Comment #13 from yangshj ---
Who can provide the test code for the recurrence of this bug
--
You are receiving this mail because:
You are the assignee for the bug.
-
To u
s are until then so my
tentative plan is to tag and release Native 1.2.x and 2.0.x on 31
May, release Native 1.2.x and 2.0.x relatively quickly, update all
Tomcat versions to use the new Native versions and then start the
June releases.
Thoughts?
Sounds good. I can set aside some time on Wedn
o tag and release Native 1.2.x and 2.0.x on 31 May, release
Native 1.2.x and 2.0.x relatively quickly, update all Tomcat versions
to use the new Native versions and then start the June releases.
Thoughts?
Sounds good. I can set aside some time on Wednesday morning to roll
10.1.x and 8.5.x as
1 May, release
Native 1.2.x and 2.0.x relatively quickly, update all Tomcat versions
to use the new Native versions and then start the June releases.
Thoughts?
Sounds good. I can set aside some time on Wednesday morning to roll
10.1.x and 8.5.x as well.
Having read the announcement, I don't t
ickly, update all Tomcat versions to
use the new Native versions and then start the June releases.
Thoughts?
Sounds good. I can set aside some time on Wednesday morning to roll
10.1.x and 8.5.x as well.
-chris
-
To unsubscribe, e
May, release Native 1.2.x and
> 2.0.x relatively quickly, update all Tomcat versions to use the new Native
> versions and then start the June releases.
>
> Thoughts?
+1
>
> Mark
>
> -
> To unsu
ase
> Native 1.2.x and 2.0.x relatively quickly, update all Tomcat versions to
> use the new Native versions and then start the June releases.
>
> Thoughts?
+1
Rémy
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat
e the new Native versions and then start the June releases.
Thoughts?
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Hi all,
It is still very in the Jakarta EE 11 development process but we already
have some changes in the main branch. Therefore I intend to start
producing milestone releases from the December release round.
Mark
-
To
This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new 845a2e2dbb New minor releases of OWB and CXF
This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch 10.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/10.0.x by this push:
new db95d2d2d8 New minor releases of OWB and CXF
This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/main by this push:
new 7ac76c6a50 New minor releases of OWB and CXF
vulnerability [2].
While this is a Spring vulnerability, it may be the case for some users
that updating Tomcat is an easier mitigation path that updating Spring.
What are the community thoughts on cancelling the current releases,
re-tagging and releasing reasonably quickly?
Possibly ok but only
Tomcat is an easier mitigation path that updating Spring.
What are the community thoughts on cancelling the current releases,
re-tagging and releasing reasonably quickly?
[1]
https://github.com/apache/tomcat/commit/1abcf3f4d741c824ae490009fe32ce300f10eddc
[2]
https://github.com/apache/tomcat
n easier mitigation path that updating Spring.
> What are the community thoughts on cancelling the current releases,
> re-tagging and releasing reasonably quickly?
>
> [1]
> https://github.com/apache/tomcat/commit/1abcf3f4d741c824ae490009fe32ce300f10eddc
>
>
ation for
> >> a current Spring vulnerability [2].
> >>
> >> While this is a Spring vulnerability, it may be the case for some users
> >> that updating Tomcat is an easier mitigation path that updating Spring.
> >> What are the community thoughts on cancellin
updating Tomcat is an easier mitigation path that updating Spring.
What are the community thoughts on cancelling the current releases,
re-tagging and releasing reasonably quickly?
Possibly ok but only if the new tag is "immediately" rather than "quickly".
I could start 10.1.x an
ting Tomcat is an easier mitigation path that updating Spring.
> What are the community thoughts on cancelling the current releases,
> re-tagging and releasing reasonably quickly?
Possibly ok but only if the new tag is "immediately" rather than "quickly".
Rémy
> Mar
on cancelling the current releases,
re-tagging and releasing reasonably quickly?
Mark
[1]
https://github.com/apache/tomcat/commit/1abcf3f4d741c824ae490009fe32ce300f10eddc
[2]
https://github.com/apache/tomcat/commit/1abcf3f4d741c824ae490009fe32ce300f10eddc
Mark,
On 3/8/22 16:24, Mark Thomas wrote:
Hi all,
I know I suggested skipping the March releases but I'd like to revisit
that in light of two things.
1. The concurrency issue I fixed earlier today. [1]
It has been present for a long time and we haven't had any bug reports.
Howeve
On 08/03/2022 23:54, Konstantin Kolinko wrote:
ср, 9 мар. 2022 г. в 00:24, Mark Thomas :
Hi all,
I know I suggested skipping the March releases but I'd like to revisit
that in light of two things.
1. The concurrency issue I fixed earlier today. [1]
It has been present for a long time a
ср, 9 мар. 2022 г. в 00:24, Mark Thomas :
>
> Hi all,
>
> I know I suggested skipping the March releases but I'd like to revisit
> that in light of two things.
>
> 1. The concurrency issue I fixed earlier today. [1]
> It has been present for a long time and w
On Tue, Mar 8, 2022 at 10:25 PM Mark Thomas wrote:
>
> Hi all,
>
> I know I suggested skipping the March releases but I'd like to revisit
> that in light of two things.
>
> 1. The concurrency issue I fixed earlier today. [1]
> It has been present for a long time and w
Hi all,
I know I suggested skipping the March releases but I'd like to revisit
that in light of two things.
1. The concurrency issue I fixed earlier today. [1]
It has been present for a long time and we haven't had any bug reports.
However, it just looks like a random timeout so u
releases with Java 11. Update change log for Java 11 switch
---
.../xreflection/ObjectReflectionPropertyInspector.java | 14 +-
webapps/docs/changelog.xml | 10 ++
2 files changed, 23 insertions(+), 1 deletion(-)
diff --git
a/java/org
Mark,
On 1/14/22 07:29, Mark Thomas wrote:
Sorry about this but while testing some updates to the Servlet TCK I
discovered my fix for [1] has broken HTTP server push for at least some,
possibly all, use cases.
I'm currently investigating and should have an update later today.
No problem. I
Hi all,
Sorry about this but while testing some updates to the Servlet TCK I
discovered my fix for [1] has broken HTTP server push for at least some,
possibly all, use cases.
I'm currently investigating and should have an update later today.
Mark
[1] https://bz.apache.org/bugzilla/show_bug
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 10.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/10.0.x by this push:
new 449c3c5 Fix building releases with Java 11
properties available in recent releases
of Java 7? I wouldn't want to trap users of Tomcat 8.5 on Java 7 into
a situation where they cannot upgrade to Tomcat 8.5.latest because
they still need the capability to control the JMX ports.
Define recent :)
If you define recent as "the thing yo
Mark,
On 1/12/22 13:36, Mark Thomas wrote:
On 12/01/2022 17:29, Christopher Schultz wrote:
On 1/10/22 11:46, Mark Thomas wrote:
So, as a first step, I intend to completely remove the
JMXLifecycleListener.
Are all those various system properties available in recent releases
of Java 7? I
On Wed, Jan 12, 2022 at 7:00 PM Mark Thomas wrote:
>
> On 11/01/2022 10:34, Michael Osipov wrote:
> > Am 2022-01-10 um 17:46 schrieb Mark Thomas:
> >> [...]
> >
> > Is this because of EJC going Java 11?
>
> No.
>
> > Has anyone reached out to them?
>
> No. Having read the thread I don't think anyt
On 12/01/2022 17:29, Christopher Schultz wrote:
On 1/10/22 11:46, Mark Thomas wrote:
So, as a first step, I intend to completely remove the
JMXLifecycleListener.
Are all those various system properties available in recent releases of
Java 7? I wouldn't want to trap users of Tomcat 8
On 11/01/2022 10:34, Michael Osipov wrote:
Am 2022-01-10 um 17:46 schrieb Mark Thomas:
[...]
Is this because of EJC going Java 11?
No.
Has anyone reached out to them?
No. Having read the thread I don't think anything we could say would
cause them to reverse their decision.
Why 11?
uses classes in sun.rmi.*. This has been deprecated since December
2019 with a warning it may be removed after 2020-12-31.
So, as a first step, I intend to completely remove the
JMXLifecycleListener.
Are all those various system properties available in recent releases of
Java 7? I wouldn'
1 - 100 of 254 matches
Mail list logo
