RFD: The fate of sun.net.www.protocol.http.HttpURLConnection.setDefaultAuthenticator

Claes Redestad claes.redestad at oracle.com
Sun Mar 10 23:15:57 UTC 2024


Hi,

Someone might have a more authoritative answer, but seeing as this is in an internal class for which we don’t publish javadoc I’d say the malformed javadoc tag is a non-issue and shouldn’t affect any decision to have this method (and the associated deprecated interface) removed. Marking internal classes/methods deprecated-for-removal is unnecessary since they're not part of the public API.

Thanks,
Claes


10 mars 2024 kl. 21:44 skrev Eirik Bjørsnøs <eirbjo at gmail.com>:

Hi,

While investigating methods annotated as @Deprecated, but with missing @deprecated javadoc tags, I discovered that sun.net.w.p.h.HttpURLConnection.setDefaultAuthenticator has a trailing period after its @deprecated tag, causing javac to not recognize it as such.

Some observations:

o The method has had this invalid @deprecated note since the initial load
o It was marked @Deprecated in Java 8
o It seems to be unused across the OpenJDK code base, including tests
o The class seems internal, given that its package is exported only to java.security.jgss

What is the right step forward here?

0: Do nothing, nobody complained so far
1: Fix the @deprecated tag issue
2: Mark the @Deprecated forRemoval=true
3: Remove the method and the private static field now
4: Something else

Thanks,
Eirik.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/net-dev/attachments/20240310/064c59c3/attachment.htm>


More information about the net-dev mailing list