public class CmdShell extends Shell
Implementation to call the CMD Shell present on Windows NT, 2000 and XP
| Constructor | Description |
|---|---|
CmdShell() |
Create an instance of CmdShell.
|
| Modifier and Type | Method | Description |
|---|---|---|
java.util.List<java.lang.String> |
getCommandLine(java.lang.String executable,
java.lang.String... arguments) |
Specific implementation that quotes all the command line.
|
equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitclone, getExecutable, getShellCommandLine, getWorkingDirectory, isDoubleQuotedArgumentEscaped, isSingleQuotedArgumentEscaped, setExecutable, setQuotedArgumentsEnabled, setWorkingDirectory, setWorkingDirectorypublic java.util.List<java.lang.String> getCommandLine(java.lang.String executable,
java.lang.String... arguments)
Specific implementation that quotes all the command line.
Workaround for http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6468220
From cmd.exe /? output:
If /C or /K is specified, then the remainder of the command line after
the switch is processed as a command line, where the following logic is
used to process quote (") characters:
1. If all of the following conditions are met, then quote characters
on the command line are preserved:
- no /S switch
- exactly two quote characters
- no special characters between the two quote characters,
where special is one of: &<>()@ˆ|
- there are one or more whitespace characters between the
the two quote characters
- the string between the two quote characters is the name
of an executable file.
2. Otherwise, old behavior is to see if the first character is
a quote character and if so, strip the leading character and
remove the last quote character on the command line, preserving
any text after the last quote character.
Always quoting the entire command line, regardless of these conditions appears to make Windows processes invoke successfully.
executable - The executable.arguments - The arguments for the executable.