-
Sub-task
-
Resolution: Fixed
-
P4
-
None
-
b10
The specification has that \@since has no structure but the test enforces a tighter spec, but possible values are broader considering all OpenJDK projects.
We should have a command line option to pass a list acceptable strings, that was each OpenJDK project can pick its own list of acceptable values.
Read the comment by roger riggs in the umbrella task for more detail.
The test should also better report how it inferred \@since values. Currently, by design, if there is no \@since then we will check the doc comment of the enclosing element.
So a user may write "\@since TBD" and the test may report "\@since 9 found; should be 24" confusing the reader on where the value "9" came from. What happens is that the test does not find an string matching the numerical values it usually expects so it looks in the doc comment of the enclosing element (Class, package, module) and uses the value if finds there.
We should have a command line option to pass a list acceptable strings, that was each OpenJDK project can pick its own list of acceptable values.
Read the comment by roger riggs in the umbrella task for more detail.
The test should also better report how it inferred \@since values. Currently, by design, if there is no \@since then we will check the doc comment of the enclosing element.
So a user may write "\@since TBD" and the test may report "\@since 9 found; should be 24" confusing the reader on where the value "9" came from. What happens is that the test does not find an string matching the numerical values it usually expects so it looks in the doc comment of the enclosing element (Class, package, module) and uses the value if finds there.
- links to
-
Commit(master) openjdk/jdk/f12d2de5
-
Review(master) openjdk/jdk/23447