* the parsing of the response body.
 * </p>
 */
public class SitemapsResponseProcessor implements ResponseProcessor {
    /** The crawler container for component lookup. */
    @Resource
    protected CrawlerContainer crawlerContainer;

    /**
     * Creates a new SitemapsResponseProcessor instance.
     */
    public SitemapsResponseProcessor() {
        super();

packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form.  A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system

# How to configure Prometheus AlertManager

Alerting with prometheus is two step process. First we setup alerts in Prometheus server and then we need to send alerts to the AlertManager.

import org.apache.maven.wagon.proxy.ProxyInfo;
import org.apache.maven.wagon.repository.Repository;
import org.codehaus.plexus.PlexusContainer;
import org.codehaus.plexus.component.repository.exception.ComponentLifecycleException;
import org.codehaus.plexus.component.repository.exception.ComponentLookupException;
import org.codehaus.plexus.logging.Logger;
import org.eclipse.aether.ConfigurationProperties;
import org.eclipse.aether.util.ConfigUtils;

import org.codehaus.plexus.util.xml.Xpp3Dom;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * JDK toolchain factory.
 * This is a <code>ToolchainFactory</code> Plexus component registered with
 * <code>jdk</code> hint.
 *
 * @since 2.0.9, renamed from <code>DefaultJavaToolchainFactory</code> in 3.2.4
 * @deprecated Use {@link org.apache.maven.api.services.ToolchainFactory} instead.
 */

     */
    public CrawlerClientFactory() {
        // NOP
    }

    /**
     * Initializes the CrawlerClientFactory.
     * Attempts to register itself with a "crawlerClientCreator" component if available.
     */
    @PostConstruct
    public void init() {
        try {
            final CrawlerClientCreator creator = crawlerContainer.getComponent("crawlerClientCreator");
            if (creator != null) {

    }

    /**
     * Initializes this component.
     */
    @PostConstruct
    public void init() {
        if (tikaConfig == null && crawlerContainer != null) {
            try {
                tikaConfig = crawlerContainer.getComponent("tikaConfig");
            } catch (final Exception e) {
                logger.debug("tikaConfig component is not found.", e);
            }
        }

Mas esse exemplo ainda é valido e mostra como interagir com os componentes internos.

///

Também podemos usar essa mesma abordagem para acessar o corpo da requisição em um manipulador de exceção.

Tudo que precisamos fazer é manipular a requisição dentro de um bloco `try`/`except`:

        DefaultRepositorySystemSession session = super.initRepoSession();
        session.setWorkspaceReader(new TestMavenWorkspaceReader());
        return session;
    }

    @Override
    protected String component() {
        return "resolver";
    }

    @Test
    void testResolutionOfASingleArtifactWhereTheArtifactIsPresentInTheLocalRepository() throws Exception {
        Artifact a = createLocalArtifact("a", "1.0");

     * If the SID has been resolved but it is is a domain SID,
     * only the domain name will be returned (e.g. MYDOM).
     * If the SID has been resolved but it is a builtin account,
     * only the name component will be returned (e.g. SYSTEM).
     * If the sid cannot be resolved the numeric representation from
     * toString() is returned.
     *
     * @return display format, potentially with resolved names
     */