java.lang.ObjectThis class is used to create operating system processes.java.lang.ProcessBuilder
Each {@code ProcessBuilder} instance manages a collection of process attributes. The #start() method creates a new Process instance with those attributes. The #start() method can be invoked repeatedly from the same instance to create new subprocesses with identical or related attributes.
Each process builder manages these process attributes:
If the value is set to {@code true}, then:
Modifying a process builder's attributes will affect processes subsequently started by that object's #start() method, but will never affect previously started processes or the Java process itself.
Most error checking is performed by the #start() method. It is possible to modify the state of an object so that #start() will fail. For example, setting the command attribute to an empty list will not throw an exception unless #start() is invoked.
Note that this class is not synchronized. If multiple threads access a {@code ProcessBuilder} instance concurrently, and at least one of the threads modifies one of the attributes structurally, it must be synchronized externally.
Starting a new process which uses the default working directory and environment is easy:
{@code
Process p = new ProcessBuilder("myCommand", "myArg").start();
}
Here is an example that starts a process with a modified working directory and environment, and redirects standard output and error to be appended to a log file:
{@code
ProcessBuilder pb =
new ProcessBuilder("myCommand", "myArg1", "myArg2");
Map env = pb.environment();
env.put("VAR1", "myValue");
env.remove("OTHERVAR");
env.put("VAR2", env.get("VAR1") + "suffix");
pb.directory(new File("myDir"));
File log = new File("log");
pb.redirectErrorStream(true);
pb.redirectOutput(Redirect.appendTo(log));
Process p = pb.start();
assert pb.redirectInput() == Redirect.PIPE;
assert pb.redirectOutput().file() == log;
assert p.getInputStream().read() == -1;
}
To start a process with an explicit set of environment variables, first call Map.clear() before adding environment variables.
Martin - Buchholz1.5 - | Nested Class Summary: | ||
|---|---|---|
| static class | ProcessBuilder.NullInputStream | Implements a null input stream. |
| static class | ProcessBuilder.NullOutputStream | Implements a null output stream. |
| abstract public static class | ProcessBuilder.Redirect | Represents a source of subprocess input or a destination of
subprocess output.
Each {@code Redirect} instance is one of the following:
Each of the above categories has an associated unique {@link Type Type}. |
| Constructor: |
|---|
|
|
| Method from java.lang.ProcessBuilder Summary: |
|---|
| command, command, command, directory, directory, environment, environment, inheritIO, redirectError, redirectError, redirectError, redirectErrorStream, redirectErrorStream, redirectInput, redirectInput, redirectInput, redirectOutput, redirectOutput, redirectOutput, start |
| Methods from java.lang.Object: |
|---|
| clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from java.lang.ProcessBuilder Detail: |
|---|
|
|
|
|
|
The returned object may be modified using ordinary Map operations. These modifications will be visible to subprocesses started via the #start() method. Two {@code ProcessBuilder} instances always contain independent process environments, so changes to the returned map will never be reflected in any other {@code ProcessBuilder} instance or the values returned by System.getenv . If the system does not support environment variables, an empty map is returned. The returned map does not permit null keys or values. Attempting to insert or query the presence of a null key or value will throw a NullPointerException . Attempting to query the presence of a key or value which is not of type String will throw a ClassCastException . The behavior of the returned map is system-dependent. A system may not allow modifications to environment variables or may forbid certain variable names or values. For this reason, attempts to modify the map may fail with UnsupportedOperationException or IllegalArgumentException if the modification is not permitted by the operating system. Since the external format of environment variable names and values is system-dependent, there may not be a one-to-one mapping between them and Java's Unicode strings. Nevertheless, the map is implemented in such a way that environment variables which are not modified by Java code will have an unmodified native representation in the subprocess. The returned map and its collection views may not obey the general contract of the Object#equals and Object#hashCode methods. The returned map is typically case-sensitive on all platforms. If a security manager exists, its checkPermission method is called with a RuntimePermission {@code ("getenv.*")} permission. This may result in a SecurityException being thrown. When passing information to a Java subprocess, system properties are generally preferred over environment variables. |
|
This is a convenience method. An invocation of the form {@code
pb.inheritIO()
}
behaves in exactly the same way as the invocation
{@code
pb.redirectInput(Redirect.INHERIT)
.redirectOutput(Redirect.INHERIT)
.redirectError(Redirect.INHERIT)
}
This gives behavior equivalent to most operating system
command interpreters, or the standard C library function
{@code system()}. |
|
If the destination is Redirect.PIPE (the initial value), then the error output of a subprocess can be read using the input stream returned by Process#getErrorStream() . If the destination is set to any other value, then Process#getErrorStream() will return a null input stream. If the redirectErrorStream attribute has been set {@code true}, then the redirection set by this method has no effect. |
This is a convenience method. An invocation of the form {@code redirectError(file)} behaves in exactly the same way as the invocation redirectError {@code (Redirect.to(file))}. |
If this property is {@code true}, then any error output generated by subprocesses subsequently started by this object's #start() method will be merged with the standard output, so that both can be read using the Process#getInputStream() method. This makes it easier to correlate error messages with the corresponding output. The initial value is {@code false}. |
If this property is {@code true}, then any error output generated by subprocesses subsequently started by this object's #start() method will be merged with the standard output, so that both can be read using the Process#getInputStream() method. This makes it easier to correlate error messages with the corresponding output. The initial value is {@code false}. |
|
If the source is Redirect.PIPE (the initial value), then the standard input of a subprocess can be written to using the output stream returned by Process#getOutputStream() . If the source is set to any other value, then Process#getOutputStream() will return a null output stream. |
This is a convenience method. An invocation of the form {@code redirectInput(file)} behaves in exactly the same way as the invocation redirectInput {@code (Redirect.from(file))}. |
|
If the destination is Redirect.PIPE (the initial value), then the standard output of a subprocess can be read using the input stream returned by Process#getInputStream() . If the destination is set to any other value, then Process#getInputStream() will return a null input stream. |
This is a convenience method. An invocation of the form {@code redirectOutput(file)} behaves in exactly the same way as the invocation redirectOutput {@code (Redirect.to(file))}. |
The new process will invoke the command and arguments given by #command() , in a working directory as given by #directory() , with a process environment as given by #environment() . This method checks that the command is a valid operating system command. Which commands are valid is system-dependent, but at the very least the command must be a non-empty list of non-null strings. If there is a security manager, its checkExec method is called with the first component of this object's {@code command} array as its argument. This may result in a SecurityException being thrown. Starting an operating system process is highly system-dependent. Among the many things that can go wrong are: In such cases an exception will be thrown. The exact nature of the exception is system-dependent, but it will always be a subclass of IOException . Subsequent modifications to this process builder will not affect the returned Process . |