[ 
https://issues.apache.org/jira/browse/DERBY-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033152#comment-14033152
 ] 

ASF subversion and git services commented on DERBY-6552:
--------------------------------------------------------

Commit 1603022 from [~dagw] in branch 'code/trunk'
[ https://svn.apache.org/r1603022 ]

DERBY-6552 The public api includes methods inherited from superclasses which 
aren't in the public api and so have no javadoc comments

Follow-up patch derby-6552-restructure-even-more. This restructures
the embedded hierarchy to avoid duplication also. It eliminates
EmbeddedBaseDataSource. Removed a slew of warnings in the IDE also by
some code washing, and regenerated the 10.11 serialized data sources
for the SerializedDataSourceTest. I removed some Javadoc from
non-public members in the API classes, and replaced them with
end-of-line comments instead (to avoid user confusion).

> The public api includes methods inherited from superclasses which aren't in 
> the public api and so have no javadoc comments
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6552
>                 URL: https://issues.apache.org/jira/browse/DERBY-6552
>             Project: Derby
>          Issue Type: Bug
>          Components: Javadoc, JDBC
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>         Attachments: derby-6552-exp.diff, derby-6552-exp.status, 
> derby-6552-restructure-even-more.diff, derby-6552-restructure-more.diff
>
>
> We simplified and cleaned up the public api in 10.11. Now, however, we've 
> lost the javadoc for methods which customers may need to use. For instance, 
> ClientDataSource contains a method called setSsl() which is inherited from 
> ClientBaseDataSourceRoot. But since ClientBaseDataSourceRoot doesn't appear 
> in the public api, there's no method header comment to consult.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to