Proposed updates to Java product versioning policy
Brent Putman
putmanb at georgetown.edu
Mon Jun 1 20:27:43 EDT 2015
On 5/29/15 2:02 PM, Cantor, Scott wrote:
>
> Please review and raise any concerns on the list, or identify anything you still think is overlooked.
>
>
>From the API section:
> # Public Java classes and methods exported from *API Packages and
> Modules* (this is defined subsequently)
> # Public Java classes and methods in any 3rd-party library shipped with
> a product and available on the classpath
As I mentioned on the call once, I think we should be explicitly clear
about what "Public" means here. I noted that an API in (specifically)
Java usually includes 'protected' methods and fields. (I.e there's no
meaningful distinction between "the API" and "the public API").
IIRC Ian agreed, but noted that "Public API" might be construed as
including those, depending on a particular language's access controls
and terminology.
Since we're talking specifically about Java here, I think it would be
less confusing to a typical Java developer if we explicitly said Java
'protected' was included in the API, rather than leaving it implicit.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150601/ae034de8/attachment.html>
More information about the dev
mailing list