Re: [VOTE] Release Apache Tomcat Connectors (JK) 1.2.50

Am 08.08.24 um 16:13 schrieb Mark Thomas: Tag: https://github.com/apache/tomcat-connectors/tree/JK_1_2_50 Source: https://github.com/apache/tomcat-connectors/tree/JK_1_2_50 Dist: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-connectors/jk/ This is a maintenance release with a handful o

(tomcat) branch main updated (043e9b3b33 -> 46f2b6bbf6)

This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git from 043e9b3b33 Simplify logic new 5583e5c5f2 Code clean-up - formatting. No functional change. new 46f2b6bbf6 Regen

(tomcat) 02/02: Regenerate with latest JavaCC (7.0.13)

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 commit 46f2b6bbf6cae325ec2bce2c74740c627adf169e Author: Mark Thomas AuthorDate: Mon Aug 12 13:46:01 2024 +0100 Regenerate wit

Re: (tomcat) 02/02: Regenerate with latest JavaCC (7.0.13)

On 12/08/2024 13:51, ma...@apache.org wrote: 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 commit 46f2b6bbf6cae325ec2bce2c74740c627adf169e Author: Mark Thomas AuthorDate: Mon

(tomcat) 02/02: Regenerate with latest JavaCC (7.0.13)

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit c8293f09339507ecc0463a415f80f4189c2e081c Author: Mark Thomas AuthorDate: Mon Aug 12 14:47:38 2024 +0100 Regenerate w

(tomcat) branch 10.1.x updated (bc85743c1e -> c8293f0933)

This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git from bc85743c1e Code clean-up - formatting. No functional change. new 36dcbb8843 Code clean-up - formatting. No functio

(tomcat) branch 9.0.x updated (f0ffcb0b9b -> 550fe372b3)

This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git from f0ffcb0b9b Code clean-up - formatting. No functional change. new e190c441ec Code clean-up - formatting. No function

(tomcat) 02/02: Regenerate with latest JavaCC (7.0.13)clear

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 550fe372b36ba75da22a7eb433a5f9c684343d84 Author: Mark Thomas AuthorDate: Mon Aug 12 15:00:12 2024 +0100 Regenerate wi

Buildbot success in on tomcat-9.0.x

Build status: Build succeeded! Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/37/builds/1040 Blamelist: Mark Thomas Build Text: build successful Status Detected: restored build Build Source Stamp: [branch 9.0.x] 550fe372b36ba75da22a7eb433a5f9c684343d84 Steps: worker_prep

Create a Tomcat 12 branch?

All, As I mentioned earlier, I am starting work on some new EL API features that will be part of Jakarta EE 12 so implemented in Tomcat 12. How do we want to handle this? My current thinking is: - create a 11.0.x branch from current main - main becomes 12.0.x I'm not expecting releases to s

(tomcat) branch main updated: Add test case for null property

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 315368925d Add test case for null property 315368925d

(tomcat) branch 10.1.x updated: Add test case for null property

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new abcb2b1faf Add test case for null property abcb2b

(tomcat) branch 9.0.x updated: Add test case for null property

This is an automated email from the ASF dual-hosted git repository. markt 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 5164db2916 Add test case for null property 5164db29

[VOTE][RESULT] Release Apache Tomcat Connectors (JK) 1.2.50

The following votes were cast: Binding: +1: markt, schultz, rjung No other votes were cast. The vote therefore passes. Thanks to everyone who contributed to this release. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat

svn commit: r70818 - /dev/tomcat/tomcat-connectors/jk/ /dev/tomcat/tomcat-connectors/jk/binaries/windows/ /dev/tomcat/tomcat-connectors/jk/binaries/windows/symbols/ /release/tomcat/tomcat-connectors/j

Author: markt Date: Mon Aug 12 21:23:50 2024 New Revision: 70818 Log: Release Tomcat Connectors (JK) 1.2.50 Added: release/tomcat/tomcat-connectors/jk/binaries/windows/symbols/tomcat-connectors-1.2.50-windows-i386-symbols.zip - copied unchanged from r70817, dev/tomcat/tomcat-connector

Buildbot failure in on tomcat-9.0.x

Build status: BUILD FAILED: failed compile (failure) Logs copied. (failure) Worker used: bb_worker2_ubuntu URL: https://ci2.apache.org/#builders/37/builds/1041 Blamelist: Mark Thomas Build Text: failed compile (failure) Logs copied. (failure) Status Detected: new failure Build Source Stamp: [branc

Re: Create a Tomcat 12 branch?

On Mon, Aug 12, 2024 at 8:30 PM Mark Thomas wrote: > > All, > > As I mentioned earlier, I am starting work on some new EL API features > that will be part of Jakarta EE 12 so implemented in Tomcat 12. > > How do we want to handle this? > > My current thinking is: > > - create a 11.0.x branch from

Re: Create a Tomcat 12 branch?

Am 12.08.24 um 20:30 schrieb Mark Thomas: All, As I mentioned earlier, I am starting work on some new EL API features that will be part of Jakarta EE 12 so implemented in Tomcat 12. How do we want to handle this? My current thinking is: - create a 11.0.x branch from current main - main beco