Dmitry, Not sure I understand the issue, but I see no reason to rollback anything. In case we have some issues, let's just fix them.
сб, 25 авг. 2018 г. в 0:53, Dmitriy Pavlov <dpavlov....@gmail.com>: > Hi Anton, > > Do you have objections about a partial rollback of changes? > > Sincerely, > Dmitriy Pavlov > > пт, 24 авг. 2018 г. в 14:24, ARomantsov <artrom...@gmail.com>: > >> Hello, Igniters. >> >> I'm testing some java keys with ignite.bat and notice that using more that >> four keys lead to internal problem and ignite.bat ignoring them all. >> >> So I created issue https://issues.apache.org/jira/browse/IGNITE-8837 and >> investigated , below what i founded >> >> 1) inside file ignite.bat happen call bin/include/parseargs.bat with next >> code to parse arguments >> set convertArgsCmd="!JAVA_HOME!\bin\java.exe" -cp "%CP%" >> org.apache.ignite.startup.cmdline.CommandLineTransformer %* >> >> 2) call of org.apache.ignite.startup.cmdline.CommandLineTransformer >> correct >> parsing JVM arguments only if they count less five >> >> 3) This problem (2) easy fix by add to set in convertArgsCmd one of next >> Java key ( -Dfile.encoding=IBM866 or -Dfile.encoding=UTF-8) >> >> 4) Like part of issue https://issues.apache.org/jira/browse/IGNITE-7135 >> it >> already had fix (3) and included in Ignite 2.4 >> >> 5) Unfortunately, when fix issue >> https://issues.apache.org/jira/browse/IGNITE-898 that key was removed >> and >> that lead to problem in 2.5 , 2.6, master >> >> What correct steps to back ignite.bat working correct on windows in >> master / >> 2.7? Both of ticket in (4) / (5) fix another problems , is correct to >> reopen >> one of them? >> >> >> >> -- >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >> >
