You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2022/05/18 19:39:00 UTC

[jira] [Resolved] (GEODE-10115) org.apache.geode.security.SecurityManager.init() declaration is inconsistent with method documentation

     [ https://issues.apache.org/jira/browse/GEODE-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinmei Liao resolved GEODE-10115.
---------------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed

> org.apache.geode.security.SecurityManager.init() declaration is inconsistent with method documentation
> ------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-10115
>                 URL: https://issues.apache.org/jira/browse/GEODE-10115
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.14.4
>            Reporter: Lynn Gallinat
>            Assignee: Jinmei Liao
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>             Fix For: 1.16.0
>
>
> org.apache.geode.security.SecurityManager.init() does not include a throws clause, but the method documentation says it throws AuthenticationFailedException.
> {noformat}
> /**
>  * Initialize the SecurityManager. This is invoked when a cache is created
>  *
>  * @param securityProps the security properties obtained using a call to
>  *        {@link DistributedSystem#getSecurityProperties}
>  * @throws AuthenticationFailedException if some exception occurs during the initialization
>  */
> default void init(Properties securityProps) {}{noformat}
> Either the throws documentation needs to be deleted, or a throws clause needs to be added.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)