Specify /D for cmd.exe to bypass the Command Processor Autorun folder

[sebthom]

With this PR I am trying to address the issue I reported at https://issues.apache.org/jira/browse/MJAVADOC-811

In corporate environments system admins may have configured a default directory for newly spawned cmd.exe processes which results in javadoc being executed in the wrong folder/wrong drive. By specifying the /D flag the cmd.exe will always execute the given command in the current working directory as expected.

The surprising AutoRun behavior is explained in Microsoft's devblog: Hidden gotcha: The command processor's AutoRun setting

[slawekjaranowski]

... the same we have in https://github.com/apache/maven-shared-utils/blob/master/src/main/java/org/apache/maven/shared/utils/cli/shell/CmdShell.java#L37

and in commons-exec ... https://github.com/apache/commons-exec/blob/master/src/main/java/org/apache/commons/exec/launcher/WinNTCommandLauncher.java ... I don't know how it is used ...

[sebthom]

... I don't know how it is used ...

maven-javadoc-plugin uses org.codehaus.plexus.util.cli.Commandline.Commandline, see https://github.com/apache/maven-javadoc-plugin/blob/ff52cff81fa6141fd2fc51f51618363e2a08f36a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L1948

which in turn uses org.codehaus.plexus.util.cli.shell.CmdShell.CmdShell()

plexus-utils/src/main/java/org/codehaus/plexus/util/cli/Commandline.java

Line 250 in a5d1ab2

setShell(new CmdShell());

[michael-o]

Will do the handling and release.