----- Original Message -----
> 
> As a follow-up to Joe Darcy's rename of jdk.Supported to jdk.Exported,
> I'd like to have another attempt at adding the annotation to a number of
> JDK specific APIs that are long standing exported, documented and
> supported APIs. Specifically, the following APIs:
> 
> - Java Debug Interface (com.sun.jdi)
> - Attach API (com.sun.tools.attach)
> - SCTP API (com.sun.nio.sctp)
> - HTTP server API (com.sun.net.httpserver)
> - Management extensions (com.sun.management)
> - JConsole Plugin API (com.sun.tools.jconsole)
> - JDK-specific API to JAAS (com.sun.security.auth)
> - JDK-specific JGSS API (com.sun.security.jgss)
> 
> (The javadoc for each of these APIs is currently generated in the build)
> 
> The webrev with the proposed update is here:
>    http://cr.openjdk.java.net/~alanb/8008662/webrev.02/
> 
> As per the original webrev, I've added package-info.java to a number of
> packages that didn't have any description. In a few cases, I've had to
> rename the legacy package.html to package-info.java.
> 
> For the review then the intention is that @jdk.Exported be added to the
> package-info and all public/protected types in these APIs. The only
> exceptions are two cases where I've added @jdk.Exported(false),
> specifically:
> 
> - com.sun.management.OSMBeanFactory as it clearly documents to stay away
> - com.sun.security.auth.callback.DialogCallbackHandler as it for the
> chop (see JEP 162)
> 
> Thanks,
> 
> Alan.
> 

I just came across this trying to understand what the new annotation means.

Is the intention for these 'exported' APIs to be eventually replaced by proper
parts of the specification (i.e. java.* or javax.*).  I'm not keen on the idea
of encouraging the use of APIs that are only in this implementation of the JDK.
-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07

Reply via email to