<modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>org.apache.maven</groupId>
    <artifactId>maven</artifactId>
    <version>4.0.0-beta-6-SNAPSHOT</version>
  </parent>

  <artifactId>maven-compat-modules</artifactId>
  <packaging>pom</packaging>

  <name>Maven Compatibility Modules</name>

  <modules>
    <module>maven-plugin-api</module>
    <module>maven-builder-support</module>

    <groupId>org.apache.maven</groupId>
    <artifactId>maven</artifactId>
    <version>4.0.0-beta-6-SNAPSHOT</version>

    <relativePath>../../</relativePath>
  </parent>

  <artifactId>maven-compat</artifactId>

  <name>Maven Compat (deprecated)</name>
  <description>Deprecated Maven2 classes maintained as compatibility layer.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>

elif _tf_api_dir not in __path__:
  __path__.append(_tf_api_dir)

# Hook external TensorFlow modules.
# Import compat before trying to import summary from tensorboard, so that
# reexport_tf_summary can get compat from sys.modules. Only needed if using
# lazy loading.
_current_module.compat.v2  # pylint: disable=pointless-statement

# Load tensorflow-io-gcs-filesystem if enabled

	// Deprecated flag, so its hidden now, existing deployments will keep working.
	cli.BoolFlag{
		Name:   "compat",
		Usage:  "enable strict S3 compatibility by turning off certain performance optimizations",
		Hidden: true,
	},
	// This flag is hidden and to be used only during certain performance testing.
	cli.BoolFlag{
		Name:   "no-compat",
		Usage:  "disable strict S3 compatibility by turning on certain performance optimizations",
		Hidden: true,

            }
        }

        /*
         * NOTE: This is primarily to keep backward-compat with Maven 2.x which did not validate that dependencies are
         * unique within a single POM. Upon multiple declarations, 2.x just kept the last one but retained the order of
         * the first occurrence. So when we're in lenient/compat mode, we have to deal with such broken POMs and mimic

~~ specific language governing permissions and limitations
~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2016-05-29
 -----

Maven Compat

 Maven2 classes maintained as compatibility layer for plugins that need to keep Maven2 compatibility.

 Plugins should avoid these classes and be updated to use only Maven3 dependencies (and require Maven3): see

        } catch (InstallationException e) {
            throw new ArtifactInstallationException(e.getMessage(), e);
        }

        /*
         * NOTE: Not used by Maven core, only here to provide backward-compat with plugins like the Install Plugin.
         */

        if (artifact.isSnapshot()) {
            Snapshot snapshot = new Snapshot();
            snapshot.setLocalCopy(true);

            }
        }

        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

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

 *
 */
@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
     */