<artifactId>maven-api</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api-di</artifactId>
  <name>Maven 4 API :: Dependency Injection</name>
  <description>Maven 4 API - Dependency Injection</description>

  <properties>
    <maven.compiler.proc>none</maven.compiler.proc>
  </properties>

        container.addComponentDescriptor(cd);

        Maven maven = container.lookup(Maven.class);
        File pom = getProject("lifecycle-listener-dependency-injection");
        MavenExecutionRequest request = createMavenExecutionRequest(pom);
        request.setGoals(Arrays.asList("validate"));
        MavenExecutionResult result = maven.execute(request);

 * specific language governing permissions and limitations
 * under the License.
 */

/**
 * Provides tools for processing Maven dependency injection annotations at compile time.
 * <p>
 * This package contains annotation processors that generate metadata files used by
 * the Maven dependency injection system. The main component is the {@link org.apache.maven.di.tool.DiIndexProcessor},

import jakarta.annotation.PostConstruct;
import jakarta.annotation.PreDestroy;
import jakarta.annotation.Resource;

/**
 * A container implementation that manages the lifecycle and dependency injection of components
 * in a crawler application. This container supports both singleton and prototype component
 * instantiation patterns.
 *
 * <p>The container provides mechanisms for:
 * <ul>

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

/**
 * Marks a method as a provider of beans for dependency injection.
 * <p>
 * This annotation can be used on static methods to programmatically create and configure
 * beans that will be managed by the dependency injection container. It's particularly
 * useful when the bean creation requires complex logic or when the bean needs to be

Each process, or "runtime", applies different constraints to the code that runs in that process.
For example, each process has different supported JVMs and a different set of services available for dependency injection.
While a lot of Gradle source code runs only in the Gradle daemon, not all of it does so.
When working on some source code it is important to be aware of the runtimes in which it will run, so that you don't break these constraints.

package org.apache.maven.model.plugin;

import org.apache.maven.model.Model;
import org.apache.maven.model.building.ModelBuildingRequest;
import org.apache.maven.model.building.ModelProblemCollector;

/**
 * Handles injection of plugin executions induced by the lifecycle bindings for a packaging.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")

     */
    public RelatedQueryHelper() {
        super();
    }

    /**
     * Initializes the RelatedQueryHelper after dependency injection is complete.
     * This method is called automatically by the dependency injection framework
     * and loads the initial related query configurations.
     */
    @PostConstruct
    public void init() {
        if (logger.isDebugEnabled()) {

 * or implied. See the License for the specific language governing permissions and limitations under
 * the License.
 */

/**
 * {@linkplain EventBus Discouraged} in favor of dependency injection and concurrency frameworks,
 * EventBus allows publish-subscribe-style communication.
 *
 * <p>See the Guava User Guide article on <a
 * href="https://github.com/google/guava/wiki/EventBusExplained">{@code EventBus}</a>.
 */

<project>
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>lifecycle-participant-reactor-dependency-injection</groupId>
    <artifactId>parent</artifactId>
    <version>1.0</version>
  </parent>

  <artifactId>module-b</artifactId>