The test expects ClassFileReconstituter restores exactly the same bytes as
original classbytes.
This can be wrong if the class has more than 1 method (due to method sorting in
the VM).
MethodParametersTarget class had only 1 method (method1), but didn't have
constructors. This caused declaration
On Fri, 4 Feb 2022 11:18:39 GMT, Alex Menkov wrote:
> The test expects ClassFileReconstituter restores exactly the same bytes as
> original classbytes.
> This can be wrong if the class has more than 1 method (due to method sorting
> in the VM).
> MethodParametersTarget class had only 1 method (
On Fri, 4 Feb 2022 11:18:39 GMT, Alex Menkov wrote:
> The test expects ClassFileReconstituter restores exactly the same bytes as
> original classbytes.
> This can be wrong if the class has more than 1 method (due to method sorting
> in the VM).
> MethodParametersTarget class had only 1 method (
On Fri, 4 Feb 2022 11:18:39 GMT, Alex Menkov wrote:
> The test expects ClassFileReconstituter restores exactly the same bytes as
> original classbytes.
> This can be wrong if the class has more than 1 method (due to method sorting
> in the VM).
> MethodParametersTarget class had only 1 method (
On Thu, 3 Feb 2022 17:44:47 GMT, Kevin Walls wrote:
>> Policy settings are no longer required to run jstatd.
>>
>> This PR is the change to the source file src/jdk.jstatd/share/man/jstatd.1
>> and in case that's hard to read, here is a diff of the text as rendered by
>> the man command:
>> ht
On Wed, 2 Feb 2022 10:54:19 GMT, Kevin Walls wrote:
> Policy settings are no longer required to run jstatd.
>
> This PR is the change to the source file src/jdk.jstatd/share/man/jstatd.1
> and in case that's hard to read, here is a diff of the text as rendered by
> the man command:
> https://
