* During code reviews that introduce new APIs, reviewers need to be mindful that all new properties are implemented with lazy types.

            form.clearSecurityInfo();
            return asIndexHtml();
        };
        validatePasswordForm(form, toIndexPage);
        if (!getUserBean().isPresent()) {
            logger.warn("User session not found during password change");
            return redirect(LoginAction.class);
        }
        final String username = getUserBean().get().getUserId();
        try {
            userService.changePassword(username, form.newPassword);

 * passed to a {@link ChildUrlsException} to be processed by the crawler.
 * </p>
 *
 * <p>
 * The class also handles potential {@link IOException}s that may occur during
 * the parsing of the response body.
 * </p>
 */
public class SitemapsResponseProcessor implements ResponseProcessor {
    /** The crawler container for component lookup. */
    @Resource

# Testen mit Überschreibungen für Abhängigkeiten { #testing-dependencies-with-overrides }

## Abhängigkeiten beim Testen überschreiben { #overriding-dependencies-during-testing }

Es gibt einige Szenarien, in denen Sie beim Testen möglicherweise eine Abhängigkeit überschreiben möchten.

Sie möchten nicht, dass die ursprüngliche Abhängigkeit ausgeführt wird (und auch keine der möglicherweise vorhandenen Unterabhängigkeiten).

# Testando Dependências com Sobreposições { #testing-dependencies-with-overrides }

## Sobrepondo dependências durante os testes { #overriding-dependencies-during-testing }

Existem alguns cenários onde você deseje sobrepor uma dependência durante os testes.

Você não quer que a dependência original execute (e nenhuma das subdependências que você possa ter).

    static Stream<Arguments> messageProvider() {
        return Stream.of(Arguments.of((String) null), Arguments.of(""));
    }

    /**
     * Validate message+cause constructor and that no interaction with cause occurs during construction.
     */
    @Test
    @DisplayName("String+Throwable ctor: sets message, cause and unsuccessful status")
    void messageAndCauseConstructor_setsFields(@Mock Throwable mockCause) {
        // Arrange

The main logic with ADRs is to describe (architectural) decisions made:

* To provide best practices and solutions we (as the *build tool* team) want to promote.
* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.

 */
package org.apache.maven.settings.building;

import java.io.PrintWriter;
import java.io.StringWriter;
import java.util.ArrayList;
import java.util.List;

/**
 * Signals one or more errors during settings building. The settings builder tries to collect as many problems as
 * possible before eventually failing to provide callers with rich error information. Use {@link #getProblems()} to
 * query the details of the failure.
 *

# Тестирование зависимостей с переопределениями { #testing-dependencies-with-overrides }

## Переопределение зависимостей во время тестирования { #overriding-dependencies-during-testing }

Есть сценарии, когда может понадобиться переопределить зависимость во время тестирования.

Вы не хотите, чтобы исходная зависимость выполнялась (и любые её подзависимости тоже).

 * under the License.
 */
package org.apache.maven.api.services;

import org.apache.maven.api.model.InputLocation;
import org.apache.maven.api.model.Model;

/**
 * Collects problems that are encountered during model building. The primary purpose of this component is to account for
 * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide