public interface BuildLauncher extends LongRunningOperation
BuildLauncher
allows you to configure and execute a Gradle build.
Instances of BuildLauncher
are not thread-safe. You use a BuildLauncher
as follows:
BuildLauncher
by calling ProjectConnection.newBuild()
.
run()
or run(ResultHandler)
to execute the build.
ProjectConnection connection = GradleConnector.newConnector() .forProjectDirectory(new File("someFolder")) .connect(); try { BuildLauncher build = connection.newBuild(); //select tasks to run: build.forTasks("clean", "test"); //include some build arguments: build.withArguments("--no-search-upward", "-i", "--project-dir", "someProjectDir"); //configure the standard input: build.setStandardInput(new ByteArrayInputStream("consume this!".getBytes())); //in case you want the build to use java different than default: build.setJavaHome(new File("/path/to/java")); //if your build needs crazy amounts of memory: build.setJvmArguments("-Xmx2048m", "-XX:MaxPermSize=512m"); //if you want to listen to the progress events: ProgressListener listener = null; // use your implementation build.addProgressListener(listener); //kick the build off: build.run(); } finally { connection.close(); }
Modifier and Type | Method and Description |
---|---|
BuildLauncher |
addProgressListener(ProgressListener listener)
Adds a progress listener which will receive progress events as the operation runs.
|
BuildLauncher |
forTasks(Iterable<? extends Task> tasks)
Sets the tasks to be executed.
|
BuildLauncher |
forTasks(String... tasks)
Sets the tasks to be executed.
|
BuildLauncher |
forTasks(Task... tasks)
Sets the tasks to be executed.
|
void |
run()
Executes the build, blocking until it is complete.
|
void |
run(ResultHandler<? super Void> handler)
Launches the build.
|
BuildLauncher |
setJavaHome(File javaHome)
If the target Gradle version supports it you can use this setting
to specify the Java home directory to use for the long running operation.
|
BuildLauncher |
setJvmArguments(String... jvmArguments)
If the target Gradle version supports it you can use this setting
to specify the Java vm arguments to use for the long running operation.
|
BuildLauncher |
setStandardError(OutputStream outputStream)
Sets the
OutputStream which should receive standard error logging generated while running the operation. |
BuildLauncher |
setStandardInput(InputStream inputStream)
If the target Gradle version supports it you can use this setting
to set the standard
InputStream that will be used by builds. |
BuildLauncher |
setStandardOutput(OutputStream outputStream)
Sets the
OutputStream which should receive standard output logging generated while running the operation. |
BuildLauncher |
withArguments(String... arguments)
Specify the command line build arguments.
|
BuildLauncher forTasks(String... tasks)
tasks
- The paths of the tasks to be executed. Relative paths are evaluated relative to the project for which this launcher was created.BuildLauncher forTasks(Task... tasks)
tasks
- The tasks to be executed.BuildLauncher forTasks(Iterable<? extends Task> tasks)
tasks
- The tasks to be executed.BuildLauncher withArguments(String... arguments)
BuildLauncher
.
Be aware that not all of the Gradle command line options are supported!
Only the build arguments that configure the build execution are supported.
They are modelled in the Gradle API via StartParameter
.
Examples of supported build arguments: '--info', '-u', '-p'.
The command line instructions that are actually separate commands (like '-?', '-v') are not supported.
Some other instructions like '--daemon' are also not supported - the tooling API always runs with the daemon.
If you specify unknown or unsupported command line option the UnsupportedBuildArgumentException
will be thrown but only at the time when you execute the operation, i.e. run()
or ModelBuilder.get()
.
For the list of all Gradle command line options please refer to the user guide
or take a look at the output of the 'gradle -?' command. Supported arguments are those modelled by
StartParameter
.
The arguments can potentially override some other settings you have configured.
For example, the project directory or Gradle user home directory that are configured
in the GradleConnector
.
Also, the task names configured by forTasks(String...)
can be overridden
if you happen to specify other tasks via the build arguments.
See the example in the docs for BuildLauncher
withArguments
in interface LongRunningOperation
arguments
- Gradle command line argumentsBuildLauncher setStandardOutput(OutputStream outputStream)
OutputStream
which should receive standard output logging generated while running the operation.
The default is to discard the output.setStandardOutput
in interface LongRunningOperation
outputStream
- The output stream.BuildLauncher setStandardError(OutputStream outputStream)
OutputStream
which should receive standard error logging generated while running the operation.
The default is to discard the output.setStandardError
in interface LongRunningOperation
outputStream
- The output stream.BuildLauncher setStandardInput(InputStream inputStream)
InputStream
that will be used by builds.
Useful when the tooling api drives interactive builds.
If the target Gradle version does not support it the long running operation will fail eagerly with
UnsupportedOperationConfigurationException
when the operation is started.
If not configured or null passed the dummy input stream with zero bytes is used to avoid the build hanging problems.
setStandardInput
in interface LongRunningOperation
inputStream
- The input streamBuildLauncher setJavaHome(File javaHome)
If the target Gradle version does not support it the long running operation will fail eagerly with
UnsupportedOperationConfigurationException
when the operation is started.
BuildEnvironment
model contains information such as Java or Gradle environment.
If you want to get hold of this information you can ask tooling API to build this model.
If not configured or null passed the sensible default will be used.
setJavaHome
in interface LongRunningOperation
javaHome
- to use for the Gradle processBuildLauncher setJvmArguments(String... jvmArguments)
If the target Gradle version does not support it the long running operation will fail eagerly with
UnsupportedOperationConfigurationException
when the operation is started.
BuildEnvironment
model contains information such as Java or Gradle environment.
If you want to get hold of this information you can ask tooling API to build this model.
If not configured, null an empty array passed then the reasonable default will be used.
setJvmArguments
in interface LongRunningOperation
jvmArguments
- to use for the Gradle processBuildLauncher addProgressListener(ProgressListener listener)
addProgressListener
in interface LongRunningOperation
listener
- The listenervoid run() throws GradleConnectionException, UnsupportedBuildArgumentException, IllegalStateException, BuildException, UnsupportedVersionException
UnsupportedVersionException
- When the target Gradle version does not support the features required for this build.UnsupportedOperationConfigurationException
- when you have configured the long running operation with a settings
like: setStandardInput(java.io.InputStream)
, setJavaHome(java.io.File)
,
setJvmArguments(String...)
but those settings are not supported on the target Gradle.BuildException
- On some failure executing the Gradle build.GradleConnectionException
- On some other failure using the connection.UnsupportedBuildArgumentException
- When there is a problem with build arguments provided by withArguments(String...)
IllegalStateException
- When the connection has been closed or is closing.void run(ResultHandler<? super Void> handler) throws IllegalStateException
handler
- The handler to supply the result to.IllegalStateException
- When the connection has been closed or is closing.