-
Notifications
You must be signed in to change notification settings - Fork 112
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
Conversation
Thanks a lot Markus! I'll take care of the warnings myself. |
@ggam Thanks! Can't wait to review your contribution! :-) |
@mkarg I already made a PR to your branch (I cannot push directly since I'm
not a repository member).
El dom., 22 abr. 2018 13:38, Markus KARG <notifications@github.com>
escribió:
… @ggam <https://github.com/ggam> Thanks! Can't wait to review your
contribution! :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#624 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACAucFKWZcSDFTxd2f8V-fxAekjXJGExks5trGvMgaJpZM4Teb5H>
.
|
abf27f7
to
166629b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* For example: | ||
* <pre> | ||
* <PRE> |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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>
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
@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. |
Signed-off-by: Markus KARG <markus@headcrashing.eu>
Signed-off-by: Markus KARG <markus@headcrashing.eu>
166629b
to
518114a
Compare
@ggam You signed with |
@mkarg yes that's the email on both sites. @waynebeaton any idea? |
ea59695
to
f61faf7
Compare
6a90447
to
03ea20f
Compare
Signed-off-by: Guillermo González de Agüero and Markus KARG <markus@headcrashing.eu>
03ea20f
to
6bf19c7
Compare
@ggam I did some checks and I need to say that the ip validation check works pretty well as soon as I replace @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. |
@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. :-) |
@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 |
There was a problem hiding this 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> |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
Improves quality of API JavaDocs by enabling JDK 8 doclint checks and fixing all WARNINGs and ERRORs (see issue #623).