[jira] [Updated] (IGNITE-1629) .NET: Introduce native logging facility.
[ https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1629: Priority: Critical (was: Blocker) > .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: Vladimir Ozerov >Priority: Critical > Labels: .net, roadmap > Fix For: 1.8 > > > 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)
[jira] [Updated] (IGNITE-1629) .NET: Introduce native logging facility.
[ https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1629: --- Summary: .NET: Introduce native logging facility. (was: .Net: Introduce native logging facility.) > .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 > Labels: .net, roadmap > Fix For: 1.8 > > > 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)
[jira] [Updated] (IGNITE-1629) .Net: Introduce native logging facility.
[ https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1629: Labels: .net roadmap (was: roadmap) > .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 > Labels: .net, roadmap > 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)
[jira] [Updated] (IGNITE-1629) .Net: Introduce native logging facility.
[ https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1629: Labels: roadmap (was: ) > .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 > Labels: roadmap > 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)
[jira] [Updated] (IGNITE-1629) .Net: Introduce native logging facility.
[ https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1629: --- Fix Version/s: 1.7 > .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: Vladimir Ozerov >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)
[jira] [Updated] (IGNITE-1629) .Net: Introduce native logging facility.
[ https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1629: Fix Version/s: (was: 1.6) > .Net: Introduce native logging facility. > > > Key: IGNITE-1629 > URL: https://issues.apache.org/jira/browse/IGNITE-1629 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Priority: Blocker > > 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)