Fix getExecCommand() to get the latest command set instead only the first…

[hAbd0u]

Currently getExecCommand() outputs only the first command get executed, even if we set a new command via setCommand(), a work around it was to reinitiate the Command class each time when setting a new command, but with this pull request the issue will be solved.

[mikehaertl]

a work around it was to reinitiate the Command class each time when setting a new command

But that is the whole point: This class really only represents one execution! Afterwards you can fetch the resulting output and error. There is no reset of this information. It's also not clear what should happen to arguments you have set: preserve them? reset them?

So whenever you want to execute a new command, you should really create a fresh new instance.

[hAbd0u]

It seems your vision is different from the name of the repository, basically when you execute a command in shell and later decide to execute another one then you are not obliged to lunch a new shell, you just use current.

[mikehaertl]

It's shell command - not shell. So one command refers to one instance. But your change basically only removes the internal caching of the executed command string. I think, it doesn't hurt if we change that. It wasn't really neccessary in the first place.

[mikehaertl]

@hAbd0u Just released 1.6.4 containing this change. Thanks for your contribution!