Kerb5Authenticator auth = new Kerb5Authenticator((Subject) null);
        assertEquals(expected, auth.isPreferredMech(oid));
    }

    @Test
    @DisplayName("Accessors: user/realm/service and lifetimes")
    void accessors_workAsExpected() {
        Kerb5Authenticator auth = new Kerb5Authenticator((Subject) null);

        // User accessors
        assertNull(auth.getUser());

    cleanCheckout: Boolean = true,
) : BasePromotionBuildType(cleanCheckout) {
    init {
        setArtifactRules(
            """
            **/build/git-checkout/platforms/core-runtime/base-services/build/generated-resources/build-receipt/org/gradle/build-receipt.properties
            **/build/git-checkout/build/distributions/*.zip => promote-build-distributions

 * subclass this factory to provide custom implementations for some of the components used by the settings builder.
 *
 * @deprecated since 4.0.0, use {@link org.apache.maven.api.services.SettingsBuilder} instead
 */
@Deprecated(since = "4.0.0")
public class DefaultSettingsBuilderFactory {

    protected SettingsReader newSettingsReader() {
        return new DefaultSettingsReader();
    }

import org.codehaus.plexus.interpolation.InterpolationPostProcessor;

/**
 * Ensures that expressions referring to URLs evaluate to normalized URLs.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
class UrlNormalizingPostProcessor implements InterpolationPostProcessor {

    private static final Set<String> URL_EXPRESSIONS;

    static {

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

/**
 * Handles expansion of general report plugin configuration into individual report sets.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
public interface ReportConfigurationExpander {

    /**

import java.util.List;

import org.apache.maven.settings.io.SettingsParseException;

/**
 * Collects problems that are encountered during settings building.
 *
 * @deprecated since 4.0.0, use {@link org.apache.maven.api.services.SettingsBuilder} instead
 */
@Deprecated(since = "4.0.0")
class DefaultSettingsProblemCollector implements SettingsProblemCollector {

    private List<SettingsProblem> problems;

    private String source;

import java.util.List;

import org.apache.maven.settings.Settings;

/**
 * Collects the output of the settings builder.
 *
 * @deprecated since 4.0.0, use {@link org.apache.maven.api.services.SettingsBuilder} instead
 */
@Deprecated(since = "4.0.0")
public interface SettingsBuildingResult {

    /**
     * Gets the assembled settings.
     *
     * @return The assembled settings, never {@code null}.

 * under the License.
 */
package org.apache.maven.settings.building;

/**
 * Collects problems that are encountered during settings building.
 *
 * @deprecated since 4.0.0, use {@link org.apache.maven.api.services.SettingsBuilder} instead
 */
@Deprecated(since = "4.0.0")
public interface SettingsProblemCollector {

    /**
     * Adds the specified problem.
     *

There are several ways to do it depending on your specific use case and the tools that you use.

You could **deploy a server** yourself using a combination of tools, you could use a **cloud service** that does part of the work for you, or other possible options.

- The Service trafficDistribution field has graduated to beta and is now available for configuration by default, without the need to enable any feature flag. Services that do not have the field configured will continue to operate with their existing behavior. Refer to the documentation https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution for more details. ([#125838](https://github.com/kuberne...