[
https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348171#comment-15348171
]
Pavel Tupitsyn commented on IGNITE-1629:
----------------------------------------
Corrections:
* Do not mess with QUIET flag in Java. Console redirection has to be done
separately (IGNITE-3363).
* Do not set console logger by default
* Provide logging to the file by default. See how Java detects that log4j is
present and uses a default config with it. Do the same with nLog in .NET. This
won't work with NuGet, but it's fine: this does not work with Maven either
> .Net: Introduce native logging facility.
> ----------------------------------------
>
> Key: IGNITE-1629
> URL: https://issues.apache.org/jira/browse/IGNITE-1629
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Blocker
> Fix For: 1.7
>
>
> This is pretty serious usability issue. Currently Ignite produces logs using
> Java "log4j" library. While naural for Java environment, this is somewhat
> alien for Windows users.
> We need to investigate ability to hack into normal .Net logging frameworks.
> This include both native Windows APIs (e.g. events), and widely-used .Net
> loggers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
