On Tue, 26 Oct 2021 00:11:02 GMT, Jonathan Gibbons <j...@openjdk.org> wrote:
>> There's old naming and new naming. We still use old naming for older >> releases, and use the new naming for recent releases. There's low-level code >> to select the right form, depending on the version. >> >> So yes, for now, the internal code is inconsistent for old/new terminology, >> and will never be completely new-clean because of declarations like >> `TypeElement`, but the important point is that the generated output should >> always be consistent, at least per the policy for that release. > > Separately, I have *long* wanted a general clean up on resource naming, > replacing the pervasive boring ubiquitous less-than-helpful `doclet.` prefix > with something more informative. I would like to see a prefix that indicates > the resource file (e.g. `tool` | `toolkit` | `html` ) and the category/kind > (such as `warning`, `error`, `help`, `content`) > > Maybe this is something to do in the next release (19). The first steps are > to decide on a naming policy and to write an internal utility that will > modify source code and resource files. Strongly related in such a utility > would be the sort the contents of the resource files. > There's old naming and new naming. We still use old naming for older > releases, and use the new naming for recent releases. There's low-level code > to select the right form, depending on the version. Interesting; could you point me in the direction of this low-level code? ------------- PR: https://git.openjdk.java.net/jdk/pull/6061
