Refactor JCmdExecutor to avoid blocking execution if stdout/stderr buffer overflow occures
If the JCmdExecutor runs an application which writes to the stdout/stderr, at a certain amount of characters the application blocks and does not terminate any more. In our tests this occurs by writing 4120 characters or more. The reason for that is, that the buffer of stdout/stderr is full and must be cleared.
Because of this we change the JCmdExecutor.run(...)
function to return the java.lang.Process
itself instead of the
JCmdExecutor.Result
object.
So every developer has full access on the process instance and can deal with it based on his own needs.