You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/04/18 12:54:00 UTC

[jira] [Updated] (IGNITE-6612) Wrap ack methods in their own class

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

Andrey Gura updated IGNITE-6612:
--------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> Wrap ack methods in their own class
> -----------------------------------
>
>                 Key: IGNITE-6612
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6612
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: None
>            Reporter: Ivan Fedotov
>            Assignee: Ivan Fedotov
>            Priority: Trivial
>              Labels: refactor
>             Fix For: 2.6
>
>
> Several methods in IgniteKernal implement similar functions: “ackAsciiLogo”, “ackConfigUrl”, “ackDaemon”, “ackOsInfo”, “ackLanguageRuntime”, “ackRemoteManagement”, “ackVmArguments”, “ackClassPaths”, “ackSystemProperties”, “ackEnviromentVariables”, “ackMemoryConfiguration”, “ackCacheConfiguration”, “ackP2PConfiguration”, “ackRebalanceConfiguration”. 
> These methods should be placed in separate class “AckVariousInformation” and called from the class instance in IgniteKernal.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)