On Tue, 3 Jun 2025 13:38:16 GMT, Sean Coffey wrote:
>> Removal of the `+thread` and `+timestamp` options that were used to control
>> the logging behavior of output from the `java.security.debug` system
>> property.
>>
>>
>> To enhance the security debug logs, the thread and timestamp data sh
> Removal of the `+thread` and `+timestamp` options that were used to control
> the logging behavior of output from the `java.security.debug` system property.
>
>
> To enhance the security debug logs, the thread and timestamp data should
> always be present. This brings it to a par with another
On Fri, 30 May 2025 14:43:32 GMT, Sean Coffey wrote:
>> Removal of the `+thread` and `+timestamp` options that were used to control
>> the logging behavior of output from the `java.security.debug` system
>> property.
>>
>>
>> To enhance the security debug logs, the thread and timestamp data s
> Removal of the `+thread` and `+timestamp` options that were used to control
> the logging behavior of output from the `java.security.debug` system property.
>
>
> To enhance the security debug logs, the thread and timestamp data should
> always be present. This brings it to a par with another
On Fri, 30 May 2025 14:26:14 GMT, Sean Mullan wrote:
> What is the behavior if someone had added these options in JDK 23 and is now
> debugging the same code with JDK 25? Are they ignored? The CSR should also
> note the behavior.
I've added this clarification to the CSR:
`Continued use of the
On Fri, 30 May 2025 08:31:31 GMT, Sean Coffey wrote:
>> Removal of the `+thread` and `+timestamp` options that were used to control
>> the logging behavior of output from the `java.security.debug` system
>> property.
>>
>>
>> To enhance the security debug logs, the thread and timestamp data s
On Fri, 30 May 2025 08:31:31 GMT, Sean Coffey wrote:
>> Removal of the `+thread` and `+timestamp` options that were used to control
>> the logging behavior of output from the `java.security.debug` system
>> property.
>>
>>
>> To enhance the security debug logs, the thread and timestamp data s
On Thu, 29 May 2025 22:36:38 GMT, Weijun Wang wrote:
> Looks great. Do you need a CSR?
Yes - need a reviewer for CSR: https://bugs.openjdk.org/browse/JDK-8358090
Thanks.
I've taken Mark's comments on board. I removed the comment referring to default
"on" also since there is no concept of on/o
> Removal of the `+thread` and `+timestamp` options that were used to control
> the logging behavior of output from the `java.security.debug` system property.
>
>
> To enhance the security debug logs, the thread and timestamp data should
> always be present. This brings it to a par with another
On Thu, 29 May 2025 19:06:15 GMT, Sean Coffey wrote:
> Removal of the `+thread` and `+timestamp` options that were used to control
> the logging behavior of output from the `java.security.debug` system property.
>
>
> To enhance the security debug logs, the thread and timestamp data should
>
On Thu, 29 May 2025 19:06:15 GMT, Sean Coffey wrote:
> Removal of the `+thread` and `+timestamp` options that were used to control
> the logging behavior of output from the `java.security.debug` system property.
>
>
> To enhance the security debug logs, the thread and timestamp data should
>
Removal of the `+thread` and `+timestamp` options that were used to control the
logging behavior of output from the `java.security.debug` system property.
To enhance the security debug logs, the thread and timestamp data should always
be present. This brings it to a par with another important s
12 matches
Mail list logo
