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

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2023/04/20 14:02:00 UTC

[jira] [Updated] (IGNITE-18010) Migrate control.sh to IgniteLogger

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

Aleksey Plekhanov updated IGNITE-18010:
---------------------------------------
    Release Note: Control-utility: Logging mechanism moved to IgniteLogger  (was: Control-utility: Loggidg mechanism moved to IgniteLogger)

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