The following are generated from this model:

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

/**
 * Provides an immutable XML processing API for Maven, offering classes and interfaces
 * for reading, manipulating, and writing XML documents in a thread-safe manner.
 * This package is used extensively for POM, settings, and other Maven configuration files.
 *
 * @since 4.0.0
 */

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

/**
 * Provides support for Maven core extensions configuration and management.
 *
 * <p>This package contains classes for:</p>
 * <ul>
 *   <li>Extension configuration model</li>
 *   <li>Extension loading and validation</li>
 *   <li>Extension lifecycle management</li>
 * </ul>
 *
 * @since 4.0.0
 */

        Model assembled = child.clone();
        assembler.assembleModelInheritance(assembled, parent, null, problems);

        // write baseName + "-actual"
        File actual = new File(
                "target/test-classes/poms/inheritance/" + baseName + (fromRepo ? "-build" : "-repo") + "-actual.xml");
        writer.write(actual, null, assembled);

        // check with getPom( baseName + "-expected" )

import junit.framework.TestCase;
import junit.framework.TestSuite;

/**
 * Suite of tests for OpenJdk 6 tests. The existence of this class is a hack because the
 * suitebuilder won't pick up the suites directly in the other classes because they don't extend
 * TestCase. Ergh.
 *
 * @author Kevin Bourrillion
 */
@AndroidIncompatible // test-suite builders
public class OpenJdk6Tests extends TestCase {
  public static Test suite() {

 This is strictly the immutable model for Maven settings in <<<org.apache.maven.api.settings>>> package.

 The following are generated from this model:

   * {{{./apidocs/index.html}Java sources}} with <<<Builder>>> inner classes for immutable instances creation.

 See also corresponding {{{../../compat/maven-settings/index.html}Maven classical settings model documentation}}.

But if for some reason your clients depend on the old behavior, you can revert to it by overriding the method `make_not_authenticated_error` in your security classes.

For example, you can create a subclass of `HTTPBearer` that returns a `403 Forbidden` error instead of the default `401 Unauthorized` error:

{* ../../docs_src/authentication_error_status_code/tutorial001_an_py310.py hl[9:13] *}

Mas, se por algum motivo seus clientes dependem do comportamento antigo, você pode voltar a ele sobrescrevendo o método `make_not_authenticated_error` nas suas classes de segurança.

Por exemplo, você pode criar uma subclasse de `HTTPBearer` que retorne um erro `403 Forbidden` em vez do erro padrão `401 Unauthorized`:

import java.lang.annotation.Inherited;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.util.Set;

/**
 * Optional features of classes derived from {@code Set}.
 *
 * @author George van den Driessche
 */
@SuppressWarnings("rawtypes") // maybe avoidable if we rework the whole package?
@GwtCompatible
public enum SetFeature implements Feature<Set> {

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

/**
 * Provides the API for the Maven build tool ({@code mvn}).
 *
 * <p>This package contains interfaces and classes specific to the main Maven build
 * tool, which is responsible for project build lifecycle execution and dependency management.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Build lifecycle execution control</li>