Currently, both the PowerShell and CMD shell executions are using deprecated APIs
to do so. As a result, each time you use this plugin, a warning is logged that
you are using a deprecated API. I have changed the plugin to use the new,
non-deprecated APIs for both PowerShell and CMD execution that were introduced
in WinRb WinRM 1.5.0. To clarify, the change that I have made is still functionally equivalent to what was being done before, but will no longer result in a warning being logged due to use of a deprecated API.
spuder
commented
8 years ago
Currently, both the PowerShell and CMD shell executions are using deprecated APIs to do so. As a result, each time you use this plugin, a warning is logged that you are using a deprecated API. I have changed the plugin to use the new, non-deprecated APIs for both PowerShell and CMD execution that were introduced in WinRb WinRM 1.5.0. To clarify, the change that I have made is still functionally equivalent to what was being done before, but will no longer result in a warning being logged due to use of a deprecated API.