[
https://issues.apache.org/jira/browse/IGNITE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931605#comment-16931605
]
Alexandr Shapkin commented on IGNITE-12176:
-------------------------------------------
I think it's worth to mention explicitly, that this PR also fixes some test
related issues.
For example, a TC build may get failed due to jvmClasspath being too long error.
> .NET: Apache.Ignite.exe fails when config has custom logger or plugins
> ----------------------------------------------------------------------
>
> Key: IGNITE-12176
> URL: https://issues.apache.org/jira/browse/IGNITE-12176
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET
>
> Steps to reproduce:
> * Implement Apache.Ignite.Core.Log.ILogger interface, compiled into assembly
> * Create a config file with that logger:
> {code}
> <configuration>
> <configSections>
> <section name="igniteConfiguration"
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
> </configSections>
> <igniteConfiguration
> xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection";>
> <logger type='CustomNs.CustomLogger, CustomAsm' />
> </igniteConfiguration>
> </configuration>
> {code}
> * Run Apache.Ignite.exe with that config file while CustomAsm is in a
> separate dir:
> {code}
> Apache.Ignite.exe -ConfigFileName=myconfig.xml -assembly=c:\w\CustomAsm.dll
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
