DiInjected diInjected = new DiInjected();
            container.lookup(org.apache.maven.di.Injector.class).injectInstance(diInjected);
            assertNotNull(diInjected.parser);
            assertNotNull(diInjected.parsers);
            assertEquals(1, diInjected.parsers.size());
            assertNotNull(diInjected.parsersMap);
            assertEquals(1, diInjected.parsersMap.size());
        }

import org.apache.maven.api.annotations.Nonnull;

/**
 * Used to configure your Mojo parameters to be injected by
 * <a href="/ref/current/maven-core/apidocs/org/apache/maven/plugin/MavenPluginManager.html">
 * <code>MavenPluginManager.getConfiguredMojo(...)</code></a>.
 * <p>
 * Beans injected into Mojo parameters are prepared by <a href="https://www.eclipse.org/sisu/">Sisu</a> JSR330-based

- DI via `@Resource` annotation
- `HtmlResponse` for JSP, `JsonResponse` for APIs

### Services
- Business logic in `app.service.*`
- Injected into Actions
- Use behavior classes to access OpenSearch

### Helpers
- Cross-cutting utilities in `helper.*`
- Stateless, injected via DI
- Access via `ComponentUtil.getFooHelper()`

## Development Notes

- **Code Style**: Enforced by `mvn formatter:format`

/**
 * Indicates that a given field will be injected with the result of
 * a dependency collection or resolution request. Whether a collection
 * or resolution request is performed is controlled by the {@link #pathScope()}
 * field, the injected field type and the {@link #requestType()}.
 * <p>
 * If the {@code requestType} is not set explicitly, it will be inferred
 * from the {@code pathScope} and the injected field type. If the type

  in terms of user-provided configuration from properties or the POM).
  If these mojos are to be first-class components, the configuration from these
  various sources must be consolidated and injected using the container.

  Currently, mojo configuration is done externally to the container, in the
  DefaultPluginManager in the maven-core API. In order to get from here to

import org.apache.maven.extension.internal.CoreExports;

/**
 */
@Named
@Singleton
@Deprecated
public class DefaultArtifactFilterManager implements ArtifactFilterManager {

    // this is a live injected collection
    protected final List<ArtifactFilterManagerDelegate> delegates;

    protected Set<String> excludedArtifacts;

    private final Set<String> coreArtifacts;

    @Inject

import static org.junit.jupiter.api.Assertions.assertFalse;

class MavenLifecycleParticipantTest extends AbstractCoreMavenComponentTestCase {

    private static final String INJECTED_ARTIFACT_ID = "injected";

    public static class InjectDependencyLifecycleListener extends AbstractMavenLifecycleParticipant {

        @Override
        public void afterProjectsRead(MavenSession session) {

 * </p>
 * <p>
 * The mojo class can also be injected with an {@link Execute} annotation to specify a
 * forked lifecycle.
 * </p>
 * <p>
 * The {@link Parameter} annotation can be added on fields to inject data
 * from the plugin configuration or from other components.
 * </p>
 * <p>
 * Fields can also be annotated with the {@link Resolution} annotation to be injected

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.lifecycle-listener.test</groupId>
  <artifactId>simple</artifactId>
  <version>1.0</version>

  <properties>
    <foo>${injected}</foo>
  </properties>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin</artifactId>
        <version>0.1</version>
        <executions>

 *
 * This is because the ModelProcessor interface extends ModelLocator and ModelReader. If we
 * made this component available under all its interfaces then it could end up being injected
 * into itself leading to a stack overflow.
 *
 * A side effect of using @Typed is that it translates to explicit bindings in the container.