[
https://issues.apache.org/jira/browse/IGNITE-17512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-17512:
--------------------------------------
Description:
We currently only load log4j2-test.xml/test.properties from the ignite config
directory. These files are not included in the test jar.
This is very inconvenient for modules that use the Ignite test framework
(extensions, for the most part).
Suggestion:
1. include log4j2-test.xml and test.properties into test jar.
2. if log4j2-test.xml/test.properties was not found in ignite config directory
- load them from the classpath.
was:
Currently we loading log4j2-test.xml/test.properties from config directory
only. These files does not include into test jar.
We currently only load log4j2-test.xml/test.properties from the ignite config
directory. These files are not included in the test jar.
This is very inconvenient for modules that use the Ignite test framework
(extensions, for the most part).
Suggestion:
1. include log4j2-test.xml and test.properties into test jar.
2. if log4j2-test.xml/test.properties was not found in ignite config directory
- load them from the classpath.
> Load logger and test configuration from the classpath.
> ------------------------------------------------------
>
> Key: IGNITE-17512
> URL: https://issues.apache.org/jira/browse/IGNITE-17512
> Project: Ignite
> Issue Type: Improvement
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Minor
> Labels: test-framework
>
> We currently only load log4j2-test.xml/test.properties from the ignite config
> directory. These files are not included in the test jar.
> This is very inconvenient for modules that use the Ignite test framework
> (extensions, for the most part).
> Suggestion:
> 1. include log4j2-test.xml and test.properties into test jar.
> 2. if log4j2-test.xml/test.properties was not found in ignite config
> directory - load them from the classpath.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
