8268549: Typo in file name in example for -Xlint:processing

[pzygielo]

Presented class is public, hence it has to be defined in AnnoProc.java.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8268549: Typo in file name in example for -Xlint:processing

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3937/head:pull/3937
$ git checkout pull/3937

Update a local copy of the PR:
$ git checkout pull/3937
$ git pull https://git.openjdk.java.net/jdk pull/3937/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3937

View PR using the GUI difftool:
$ git pr show -t 3937

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3937.diff

[bridgekeeper]

Hi @pzygielo, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user pzygielo" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

[pzygielo]

/signed

[openjdk]

@pzygielo The following label will be automatically applied to this pull request:

• compiler

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[bridgekeeper]

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

[pzygielo]

I'm listed at OCAs submitted prior to 2021 (gh:pzygielo). What else can I do to have OCA confirmed and move it forward?

[pzygielo]

What can I do to move it forward?

[kevinrushforth]

What can I do to move it forward?

You need to update the PR with the JBS bug ID (9070572 was the temporary incident ID), which is 8268549 -- see JDK-8268549. You also need to make sure that this PR title matches that of the JBS bug.

[pzygielo]

Commit message/PR title updated. Also required change of import implemented.

[mlbridge]

Webrevs

• 00: Full (a8dffed8)

[kevinrushforth]

@pzygielo For future reference, please do not force-push to a branch once the associated PR is under review. It makes incremental reviews more difficult. If you need to push additional changes, just add new commits. Similarly, if you need to update your branch with additional commits from master, please merge rather than rebase.

[pzygielo]

do not force-push to a branch once the associated PR is under review.
just add new commits.
merge rather than rebase.

Understood. I'm sorry for the troubles.

[pzygielo]

Perhaps this change in method name in example could be considered for this bug as well? It's in the same file. I can push additional commit to this branch if accepted.

[lgxbslgx]

@pzygielo Thanks for your contribution. The man documentations, like *.1, are generated from the original Markdown files by using some tools. So we can't directedly revise these *.1 files. Some comments from another example are linked here for you.

This change is somewhat problematic. The nroff man files are generated from Markdown files which are not (yet) open source. Don't ask: long story; we're working on it.

The bottom line is that this change should really be made to the upstream Markdown file. Direct changes to this file are at risk of being overwritten at some point in the future.

Currently, in order to solve this issue, we can report it to the oracle employees and get their help to revise the original files.
Could @kevinrushforth or anyone else from oracle take a look?

I see that the Assignee of this bug is @jonathan-gibbons. Maybe he can give more information and help, too.

[pzygielo]

@lgxbslgx thanks for checking and linking example. Hope it can be fixed in sources then.

[pzygielo]

I think there is also chance to fix source for line 2114

jdk/src/jdk.compiler/share/man/javac.1

Lines 2112 to 2114 in e9b2c05

	The compiler generates this warning when you have a class that has an
	annotation, and you use an annotation processor that cannot handle that
	type of exception.

as I suppose it shall be type of annotation.

[pzygielo]

Closing with the hope it would be fixed in the source.

[jonathan-gibbons]

I'll fix the issues upstream.