Hi,
If it helps, commons weaver (
https://commons.apache.org/proper/commons-weaver/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/index.html)
can help for the backport part (enable or not the run in build.xml).
Romain
Le dim. 2 oct. 2022 à 06:42, Christopher
Emmanuel,
On 9/28/22 11:05, Emmanuel Bourg wrote:
The security manager has been deprecated for removal in Java 17 [1], and
at some point Tomcat will have to stop supporting it.
Do we want to wait until it's no longer available in the JDK to remove
it from Tomcat, or should we remove it earlie
> 2022年9月29日 00:16，Rémy Maucherat 写道：
>
> On Wed, Sep 28, 2022 at 5:41 PM Mark Thomas wrote:
>>
>> On 28/09/2022 16:05, Emmanuel Bourg wrote:
>>> Hi all,
>>>
>>> The security manager has been deprecated for removal in Java 17 [1], and
>>> at some point Tomcat will have to stop supporting it
On Wed, Sep 28, 2022 at 5:41 PM Mark Thomas wrote:
>
> On 28/09/2022 16:05, Emmanuel Bourg wrote:
> > Hi all,
> >
> > The security manager has been deprecated for removal in Java 17 [1], and
> > at some point Tomcat will have to stop supporting it.
> >
> > Do we want to wait until it's no longer a
On 28/09/2022 16:05, Emmanuel Bourg wrote:
Hi all,
The security manager has been deprecated for removal in Java 17 [1], and
at some point Tomcat will have to stop supporting it.
Do we want to wait until it's no longer available in the JDK to remove
it from Tomcat, or should we remove it earl
Hi all,
The security manager has been deprecated for removal in Java 17 [1], and
at some point Tomcat will have to stop supporting it.
Do we want to wait until it's no longer available in the JDK to remove
it from Tomcat, or should we remove it earlier, maybe in Tomcat 10.1 or 11?
I tend to
