You can also create a container instance using a <<custom_gradle_types.adoc#read_only_managed_properties,read-only managed property>>.

====
include::sample[dir="snippets/providers/collections/kotlin",files="build.gradle.kts[tags=ndoc]"]

----

In the example above, a deployment task is created dynamically for every user-configured environment.

You can find out more about implementing project extensions in <<custom_gradle_types.adoc#custom_gradle_types,Developing Custom Gradle Types>>.

[[modeling_dsl_like_apis]]
== Modeling DSL-like APIs
DSLs exposed by plugins should be readable and easy to understand.

====

==== Next to the property declaration

You may configure a convention on a lazy property next to the place where the property is declared.
Note this option is not available for <<custom_gradle_types.adoc#managed_properties,managed properties>>, and has the same caveats as configuring a convention from the task constructor.

====

    /**
     * Types that are allowed to be instantiated directly by Gradle when exposed as a getter on a type.
     *
     * @implNote Keep in sync with platforms/documentation/docs/src/docs/userguide/extending-gradle/custom_gradle_types.adoc
     * @see ManagedObjectFactory#newInstance
     */
    private static final ImmutableSet<Class<?>> MANAGED_PROPERTY_TYPES = ImmutableSet.of(
        ConfigurableFileCollection.class,

You can access it by <<custom_gradle_types#service_injection, injecting>> the link:{javadocPath}/org/gradle/api/configuration/BuildFeatures.html[`BuildFeatures`] service into your code.

Gradle uses runtime class decoration to implement abstract methods as long as the object is instantiated via `ObjectFactory` or some other automatic mechanism (like <<custom_gradle_types.adoc#managed_properties,managed properties>>).
Those methods should never be directly implemented.

==== Wrapper task configuration