On 5/27/21 6:31 AM, Erik Joelsson wrote:
On Thu, 27 May 2021 13:05:27 GMT, Hannes Wallnöfer <hann...@openjdk.org> wrote:
make/Docs.gmk line 336:
334:
335: # Add summary pages for new/deprecated APIs in recent releases
336: $1_OPTIONS += --since 12,13,14,15,16,17 --since-label "New API since JDK
11"
How do you expect this to change as the JDK version is bumped? If there is an
expected pattern, then maybe we should try to generate the list instead, so we
don't need to manually update twice a year.
I don't have a solution for this problem. AFAIK there are a few things that have to be
"bumped" manually between releases, and this would be yet another. Obviously
not a great solution.
Yes, there are a few things, but in the build itself, we are down to a single config file
today, so I would really appreciate if this could be figured out. I can provide the
implementation for generating this, but I need to understand what the expected pattern
is. From what I can see, it looks like $(sequence N, M) where N is the last LTS+1 and M
is current JDK version. Then the string has "JDK N" in it. M is already well
defined, so the only new input here is N, which we could move to the version numbers
config file (make/conf/version-numbers.conf). Something like
DEFAULT_VERSION_DOCS_API_SINCE=11. There is some additional boilerplate needed, and the
sequence macro of course, but does this sound reasonable to you?
The ability to reduce the configuration down to a single number, like
DEFAULT_VERSION_DOCS_API_SINCE=11, seems like a good solution until we
think of anything better. The issue will be how long we stay with 11,
and what do we move to after that, and when?
-- Jon
-------------
PR: https://git.openjdk.java.net/jdk/pull/4209
