[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR(S): 7034834 JVMTI xml file referring to old JDK version
From:       "serguei.spitsyn () oracle ! com" <serguei ! spitsyn () oracle ! com>
Date:       2016-12-05 3:19:14
Message-ID: 9670ebbe-221c-f005-710c-3c1d13a60f68 () oracle ! com
[Download RAW message or body]

Hi David,


On 12/4/16 19:12, David Holmes wrote:
> Hi Serguei,
>
> Looks okay.

Thank you a lot!

>
> Ideally there would be some way to use a symbolic reference instead of 
> hard wiring 7, 8 or 9. These are the kinds of paths that should be 
> specified relative to some base URL that need only be set once. But I 
> don't see that occurring in the JDK code either.

I did not find yet how to express it in the xml format.
Maybe, it is possible to do some XSL/T transformation.
But I've not found a good approach either.

Thanks,
Serguei

>
> Thanks,
> David
>
> On 3/12/2016 4:54 PM, serguei.spitsyn@oracle.com wrote:
>> Please, review a fix for the bug:
>>   https://bugs.openjdk.java.net/browse/JDK-7034834
>>
>> Webrev:
>> http://cr.openjdk.java.net/~sspitsyn/webrevs/2016/hotspot/7034834-Doc.hs1/ 
>>
>>
>>
>> Summary:
>>
>>    The JVM TI spec has links to the old JDK 7 release documents.
>>    The fix is to make it up-to-date and link to the JDK 9 docs.
>>
>>
>> One issue with the fix that the JDK 9 doc pages do not exist yet.
>> I hope that the JDK 9 release doc pages will be created the same way as
>> they were for JDK 8.
>> The JVM TI spec for JDK 8 has the same problem as it also has links to
>> the JDK 7 release documents.
>> I'd like to fix this issuein the JDK 9 ASAP to be able to backport the
>> fix to JDK 8.
>>
>>
>> Thanks,
>> Serguei

[prev in list] [next in list] [prev in thread] [next in thread]