// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

[[custom_gradle_types]]
= Developing Custom Gradle Types

This page has been removed.

[[managed_properties]]

[[read_only_managed_properties]]

[[read_only_managed_nested_properties]]

    override fun execute(parameters: Params) {

    }
}
----

The `execute` method must be implemented because this is where the work happens.
An action implementation is treated as a <<custom_gradle_types.adoc#custom_gradle_types,custom Gradle type>> and can use any of the features available to custom Gradle types.
In particular, some Gradle services can be injected into the implementation.

A dataflow action may accept parameters.

[source,groovy]
----
abstract class BaseCountingService implements BuildService<CountingParams>, AutoCloseable {

}
----

A build service implementation is treated as a <<custom_gradle_types.adoc#custom_gradle_types,custom Gradle type>> and can use any of the features available to custom Gradle types.

A build service can optionally take parameters, which Gradle injects into the service instance when creating it.

    static final String CUSTOM_GRADLE_TASK_DOC_LINK = "Rewrite the class with a constructor injection. " + new DocumentationRegistry().getDocumentationRecommendationFor("information on developing custom gradle task types", "custom_gradle_types", "service_injection");

    private final CrossBuildInMemoryCache<Class<?>, CachedConstructor> constructorCache;
    private final ClassGenerator classGenerator;

<4> Add an instance of the newly created class as JVM argument provider to the integration test task.footnote:managedTypes[The `CommandLineArgumentProvider` in this example is implemented as a <<custom_gradle_types.adoc#custom_gradle_types,managed type>>.]

=== Ignoring system properties

It may be necessary to ignore some system properties as inputs as they do not influence the outcome of the integration tests.

 *
 * <p>Gradle will attempt to instantiate a nested bean on abstract getter methods annotated with this annotation.
 * This creates a <a href="https://docs.gradle.org/current/userguide/custom_gradle_types.html#read_only_managed_nested_properties">read-only managed nested property</a>.</p>
 *
 * <p>The implementation of the nested bean is tracked as an input, too.

[source,java]
----
include::{snippetsPath}/java/toolchain-management/groovy/buildSrc/src/main/java/org/myorg/JavaToolchainResolverPlugin.java[tags=java-toolchain-resolver-plugin]
----
<1> The plugin uses <<custom_gradle_types.adoc#property_injection,property injection>>, so it must be `abstract` and a settings plugin.

The parameters must be represented using <<custom_gradle_types.adoc#managed_properties,managed properties>> and the parameters type must be a <<custom_gradle_types.adoc#managed_types,managed type>>.
You can use an interface or abstract class declaring the getters and Gradle will generate the implementation.

 * {@link org.gradle.kotlin.dsl.DependenciesExtensions extension functions for Kotlin DSL}.
 * <p>
 * @see <a href="https://docs.gradle.org/current/userguide/custom_gradle_types.html#custom_dependencies_blocks">Creating custom dependencies blocks.</a>
 *
 * @since 7.6
 */
@Incubating
@SuppressWarnings("JavadocReference")
public interface Dependencies {
    /**

include::logging.adoc[leveloffset=+2]
include::potential_traps.adoc[leveloffset=+2]
include::build_environment.adoc[leveloffset=+2]
include::init_scripts.adoc[leveloffset=+2]
include::custom_gradle_types.adoc[leveloffset=+2]
include::build_services.adoc[leveloffset=+2]
include::dataflow_actions.adoc[leveloffset=+2]
include::test_kit.adoc[leveloffset=+2]
include::ant.adoc[leveloffset=+2]

[[part:jvm_projects]]