Hi Gianfranco,
I don't understand exactly what we are talking about :)
If we are about https://issues.apache.org/jira/browse/IGNITE-923, then
- It has to be fixed in a separate thread (don't do it together with
IGNITE-788).
- If you have any objections about the way to fix IGNITE-923. Can you
I fix it in a separate branch, I'd like to discuss the other JIRA (IGNITE
788 ) implementation details. I have finished the implementation and I
commit a patchi in the JIRA as soon as possible.
Thanks, Gianfranco
2015-05-26 17:35 GMT+02:00 Gianfranco Murador murador.gianfra...@gmail.com
:
Hi
On Tue, May 26, 2015 at 8:40 AM, Gianfranco Murador
murador.gianfra...@gmail.com wrote:
I fix it in a separate branch, I'd like to discuss the other JIRA (IGNITE
788 ) implementation details. I have finished the implementation and I
commit a patchi in the JIRA as soon as possible.
Thanks,
Hi Artiom,
The method implementation ( isQuite() ) is in ingnite-log4j, so I'd like
to fix the implementation in the same branch, that's it.
Regards,
Gianfranco
2015-05-26 11:43 GMT+02:00 Artiom Shutak ashu...@gridgain.com:
Hi Gianfranco,
I don't understand exactly what we are talking about
Hi, Igniters,
In process of investigation of a user request Disable ignite console logs
(
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330),
I've found inconsistency at implementations of IgniteLogger.isQuiet():
- Javadoc of the method says:
/**
