[
https://issues.apache.org/jira/browse/IGNITE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627185#comment-17627185
]
Ignite TC Bot commented on IGNITE-18010:
----------------------------------------
{panel:title=Branch: [pull/10354/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10354/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6879191&buildTypeId=IgniteTests24Java8_RunAll]
> Migrate control.sh to IgniteLogger
> ----------------------------------
>
> Key: IGNITE-18010
> URL: https://issues.apache.org/jira/browse/IGNITE-18010
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: IEP-81
> Fix For: 2.15
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Right now control.sh utility uses own logging mechanism built on
> java.util.logging while other parts of Ignite uses IgniteLogger facade.
> It will be more convenient and consistent to use IgniteLogger in control.sh
> code too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
