Yes, MinIO will try to transparently migrate any existing IAM data and either stores
it in plaintext (no KMS) or re-encrypts using the KMS.

> Is this change backward compatible? Will it break my setup?

This change is not backward compatible for all setups. In particular, the native
Hashicorp Vault integration - which has been deprecated already - won't be

 *
 */
@Deprecated
public interface WagonManager extends org.apache.maven.repository.legacy.WagonManager {
    /**
     * this method is only here for backward compat (project-info-reports:dependencies)
     * the default implementation will return an empty AuthenticationInfo
     *
     * @param id an id
     * @return corresponding authentication info
     */

import org.apache.maven.bridge.MavenRepositorySystem;
import org.apache.maven.plugin.LegacySupport;
import org.apache.maven.project.ProjectBuilder;

/**
 * This realizes the metadata source via the default hint to provide backward-compat with Maven 2.x whose Plexus version
 * registered component descriptors twice: once keyed by role+roleHint and once keyed by role only. This effectively

	<component name="pingJob" class="org.codelibs.fess.job.PingSearchEngineJob" instance="prototype">
	</component>
	<component name="pythonJob" class="org.codelibs.fess.job.PythonJob" instance="prototype">
	</component>
	<!-- Backward Compatibility  -->
	<component name="pingEsJob" class="org.codelibs.fess.job.PingSearchEngineJob" instance="prototype">
	</component>

                    problemMessage, actualMessages);
            assertTrue(false, message);
        }

        return this;
    }

    // Helper method for backward compatibility
    static ProjectBuildingResultWithProblemMessageAssert projectBuildingResultWithProblemMessage(String message) {
        return new ProjectBuildingResultWithProblemMessageAssert(null).hasProblemMessage(message);

 * <p>
 * This class now uses the standard {@link java.util.Base64} implementation
 * instead of a custom implementation, providing better security and performance.
 * The API remains backward compatible with previous versions.
 * </p>
 *
 * @author higa
 */
public abstract class Base64Util {

    /**
     * Do not instantiate.
     */
    protected Base64Util() {
    }

    /**

 * under the License.
 */
package org.apache.maven.plugin;

import org.apache.maven.execution.MavenSession;
import org.eclipse.aether.RepositorySystemSession;

/**
 * Helps to provide backward-compatibility with plugins that use legacy components. <strong>Warning:</strong> This is an
 * internal utility interface that is only public for technical reasons, it is not part of the public API. In

// - total size of the bucket
// - total objects in a bucket
// - object size histogram per bucket
type BucketUsageInfo struct {
	Size uint64 `json:"size"`
	// Following five fields suffixed with V1 are here for backward compatibility
	// Total Size for objects that have not yet been replicated
	ReplicationPendingSizeV1 uint64 `json:"objectsPendingReplicationTotalSize"`

            }
        }

        RemoteRepository remoteRepo = RepositoryUtils.toRepo(deploymentRepository);
        /*
         * NOTE: This provides backward-compat with maven-deploy-plugin:2.4 which bypasses the repository factory when
         * using an alternative deployment location.
         */
        if (deploymentRepository instanceof DefaultArtifactRepository

        return this;
    }

    private String formatLocation(int columnNumber, int lineNumber) {
        return String.format("line %d, column %d", lineNumber, columnNumber);
    }

    // Helper method for backward compatibility
    static ProjectBuildingResultWithLocationAssert projectBuildingResultWithLocation(int columnNumber, int lineNumber) {