Note that when adding a lazy property to an existing class, you need to check if instances of the class are instantiated via ObjectFactory. Most classes are instantiated this way, but it's possible that a class without any lazy properties was never updated to use it. A tell-tale sign that an object is not instantiated via the ObjectFactory are direct calls to the constructor with new.

### Existing properties in existing classes

import java.lang.annotation.Retention;

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Denotes that a bean should be created as a singleton instance.
 * <p>
 * Singleton-scoped beans are instantiated once and reused throughout the entire
 * Maven execution. This scope should be used for stateless services or components
 * that can be safely shared across the entire build process.
 * <p>
 * Example usage:
 * <pre>

import com.google.inject.ScopeAnnotation;

import static java.lang.annotation.ElementType.TYPE;
import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before session execution starts
 * and discarded after session execution completes.
 *
 * @since 3.2.0
 */
@Target({TYPE})
@Retention(RUNTIME)
@ScopeAnnotation

import static java.lang.annotation.ElementType.METHOD;
import static java.lang.annotation.ElementType.TYPE;
import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before session execution starts
 * and discarded after session execution completes.
 * <p>
 * A {@code org.apache.maven.api.Session} object is available in the scope of this annotation.
 *
 * @since 4.0.0
 */

Runtime decoration mixes in methods that use Groovy Closures to maintain consistent behavior in Groovy DSL.

import com.google.inject.ScopeAnnotation;

import static java.lang.annotation.ElementType.TYPE;
import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Indicates that annotated component should be instantiated before mojo execution starts and discarded after mojo
 * execution completes.
 *
 * @since 3.1.2
 */
@Target({TYPE})
@Retention(RUNTIME)
@ScopeAnnotation

import org.gradle.api.tasks.Internal
import org.gradle.work.DisableCachingByDefault
import java.io.File
import kotlin.io.path.invariantSeparatorsPathString


@DisableCachingByDefault(because = "Abstract super-class, not to be instantiated directly")
abstract class SubprojectsInfo : DefaultTask() {

    private
    val rootPath = project.layout.projectDirectory.asFile.toPath()

    private

 * to test functionality that requires rea distributions (like the wrapper)
 * or separately published libraries (like the Tooling API Jar).
 */
@DisableCachingByDefault(because = "Abstract super-class, not to be instantiated directly")
abstract class DistributionTest : Test() {

    /**
     * To further categorize tests. (We should simplify this and get rid of the subclasses if possible)
     */
    @get:Internal

* MojoDescriptor

  Remove set/getMojoConfiguration(..), as it will become obsolete.

* MavenSession

  We may need to enable the context injection here, since this will be
  instantiated per-project. If we always inject the same context parameters,
  and are careful to inject nulls where things are missing, we should be

    @Override
    void render(File htmlReportFile, RichReportData data) {
        super.render(htmlReportFile, enrichReport(data))
    }

    /**
     * This is super-hacky: this report is instantiated via {@code newInstance()}, within a different
     * classloader by {@link JApiCmpWorkerAction}, so there is no way to use a
     * normal property on the renderer instance and just set the location of the API file in it.
     *