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

2018-06-26 Thread Dmitriy Pavlov (JIRA) 


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

Dmitriy Pavlov updated IGNITE-6612:
---
Fix Version/s: (was: 2.6)
   2.7

> 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.7
>
>
> 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)

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

2018-04-18 Thread Andrey Gura (JIRA) 

 [ 
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)

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

2018-01-19 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-6612:

Fix Version/s: (was: 2.4)
   2.5

> 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.5
>
>
> 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)

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

2017-10-31 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-6612:

Fix Version/s: (was: 2.3)
   2.4

> 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.4
>
>
> 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
(v6.4.14#64029)