Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling JDK 8 Doclint Checks (#623) #624

Merged
merged 3 commits into from
May 19, 2018

Conversation

mkarg
Copy link
Contributor

@mkarg mkarg commented Apr 21, 2018

Improves quality of API JavaDocs by enabling JDK 8 doclint checks and fixing all WARNINGs and ERRORs (see issue #623).

@mkarg mkarg added help wanted Extra attention is needed good first issue Good for newcomers javadoc labels Apr 21, 2018
@mkarg mkarg added this to the 2.2 milestone Apr 21, 2018
@mkarg mkarg self-assigned this Apr 21, 2018
@mkarg mkarg added the wip label Apr 21, 2018
@ggam
Copy link
Contributor

ggam commented Apr 22, 2018

Thanks a lot Markus! I'll take care of the warnings myself.

@mkarg
Copy link
Contributor Author

mkarg commented Apr 22, 2018

@ggam Thanks! Can't wait to review your contribution! :-)

@ggam
Copy link
Contributor

ggam commented Apr 22, 2018 via email

@mkarg mkarg changed the title WIP: Enabling JDK 8 Doclint Checks (#623) Enabling JDK 8 Doclint Checks (#623) Apr 22, 2018
@mkarg mkarg removed good first issue Good for newcomers help wanted Extra attention is needed labels Apr 22, 2018
@mkarg mkarg requested review from chkal and asoldano April 22, 2018 14:03
@mkarg mkarg removed the wip label Apr 22, 2018
Copy link
Contributor

@chkal chkal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just added a few comments.

BTW: This PR also contains the commits from #622 which is a bit confusing. But I guess the plan is to rebase this after #622 gets merged, correct?

* For example:
* <pre>
* <PRE>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wondering: Are uppercase <pre> tags enforced by doclint? I'm just asking, because all other HTML elements are lowercase.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strange but true, but on my machine this actually did fix a Doclint complaint. Maybe a bug in Doclint, I don't know really.

@@ -45,8 +45,8 @@
public List<String> getRequestHeader(String name);

/**
* Get a HTTP header as a single string value.
* <p/>
* <p>Get a HTTP header as a single string value.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I may be too niggling here, but IMO we should either put both the start and end element on a line nor non of them.

So either:

<p>
Foobar
</p>

Or:

<p>Foobar</p>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no feelings at all about that. My intention was to touch as few lines as possible to make the PR at-most reviewable. I abstained form applying any style at all, because we do not have agreed upon a particular style, and the current Javadocs seems to be chaotic. The original docs were even mixing br and p... So really, my PR is just a real bug fix, nothing else.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that your PR definitely improves the situation. It's just something that came to my mind while reviewing this.

@mkarg
Copy link
Contributor Author

mkarg commented Apr 28, 2018

@chkal Sorry for the confusion. Yes, the expected scenario is that I will merge #622 first if no -1 is voted within the next 7 days.

@mkarg
Copy link
Contributor Author

mkarg commented May 5, 2018

@eclipsewebmaster I do not understand why ip validation fails. It says @ggam's signed-off-by is invalid, but in fact it looks pretty valid.

mkarg added 2 commits May 8, 2018 13:01
Signed-off-by: Markus KARG <markus@headcrashing.eu>
Signed-off-by: Markus KARG <markus@headcrashing.eu>
@mkarg
Copy link
Contributor Author

mkarg commented May 8, 2018

@ggam You signed with Signed-off-by: Guillermo González de Agüero <z06.guillermo@gmail.com>. Is that the exact same email address you also registered with your Eclipse Foundation account and Github account? Otherwise this would explain why the ip-validation check still fails.

@ggam
Copy link
Contributor

ggam commented May 8, 2018

@mkarg yes that's the email on both sites. @waynebeaton any idea?

@mkarg
Copy link
Contributor Author

mkarg commented May 8, 2018

@mkarg mkarg force-pushed the mkarg-enabling-doclint branch 4 times, most recently from ea59695 to f61faf7 Compare May 10, 2018 09:31
@mkarg mkarg force-pushed the mkarg-enabling-doclint branch 5 times, most recently from 6a90447 to 03ea20f Compare May 10, 2018 09:54
Signed-off-by: Guillermo González de Agüero and Markus KARG <markus@headcrashing.eu>
@mkarg
Copy link
Contributor Author

mkarg commented May 10, 2018

@ggam I did some checks and I need to say that the ip validation check works pretty well as soon as I replace z06.guillermo@gmail.com by my own email address. It even works if I write your full name with all umlauts and accents into the sign-off. So it MUST be the wrong address! Please do check once more that you really filed exactly that address with all your paperwork and that this really is the address linked with your ggam account on both, Github user account and Eclipse Foundation user account.

@eclipsewebmaster Can you please check the actual reason why the ip-validation of user ggam fails always? Maybe you can see the address actually expected for that user account?

Meanwhile I signed your commit with my address and added both user names. This is pretty legal as the ip check wants EITHER you or me to sign all commits. This seems to work so we can go on with this PR.

@mkarg mkarg requested a review from jimma May 10, 2018 10:06
@mkarg
Copy link
Contributor Author

mkarg commented May 10, 2018

@chkal Can you please redo your approval? This is needed as the recent fixing of signed-off-by problems with ggam's contribution invalidated your existing voting.

@jimma I would be more than happy if you would approve this PR. It is an extension to the PR #622 which you approved recently. Thanks. :-)

@chkal
Copy link
Contributor

chkal commented May 10, 2018

@mkarg Actually I didn't approve the changes yet, I just added the comments. I'll need some time to checkout your changes and verify the generated Javadocs. A few aspects look weird to me (before and after your changes) and I want to verify the resulting HTML just to check that everything is fine (like @NameBinding which doesn't contain paragraph tags at all). I'll come back to you ASAP.

@spericas spericas self-requested a review May 16, 2018 15:04
Copy link
Contributor

@chkal chkal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay. I finally found some time to check some changes by comparing the new javadocs with the old ones.

I think that almost all the fixes are fine. I'm just a bit unsure regarding all the <p> element changes. There is at least one case for which the rendered output now differs from the original (see my comment). And IMHO the original looks better. Unfortunately repairing all these <p> elements is quite difficult and even the original javadocs don't always render in a nice way.

However, I'll approve the PR now. IMO it is important to enable the doclint checks. We can further cleanup the HTML later on to improve the visual output.

@@ -25,7 +25,7 @@
/**
* Meta-annotation used to create name binding annotations for filters
* and interceptors.
* <p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After removing this <p>, the upper sentence isn't in its own paragraph any more. I don't think that this is correct. The rendered page looks weird, because there is no spacing between the first paragraph and the source code any more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will merge now but ask some rookie volunteer to improve the layout of the HTML.

@mkarg mkarg merged commit e9d0335 into jakartaee:master May 19, 2018
@mkarg mkarg deleted the mkarg-enabling-doclint branch June 2, 2018 13:59
@mkarg mkarg added the project label Dec 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants