# Python config is the same across all containers because the binary is the same
build:rbe_linux_cpu --python_path="/usr/bin/python3"
# These you may need to change for your own GCP project.
common:rbe_linux_cpu --remote_instance_name=projects/tensorflow-testing/instances/default_instance

# TODO(kanglan): Remove it after toolchain update is complete.
build:rbe_linux_cpu_old --config=rbe_linux

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-t06</groupId>
  <artifactId>p0</artifactId>
  <packaging>pom</packaging>
  <name>p0</name>
  <version>1.0</version>
  <organization>
    <name>Codehaus</name>
  </organization>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t06-a</artifactId>
        <version>1.0</version>
      </dependency>

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.1.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.1.0 https://maven.apache.org/xsd/maven-4.1.0.xsd">
    <modelVersion>4.1.0</modelVersion>

    <groupId>test</groupId>
    <artifactId>test</artifactId>
    <version>0.1-SNAPSHOT</version>

    <dependencyManagement>
        <dependencies>

        }

        def project = model.getClassDoc(Project.class.name)

        blocksTable.tr.each { Element tr ->
            mergeBlock(tr, project)
        }
    }

    def mergeBlock(Element tr, gradlebuild.docs.dsl.docbook.model.ClassDoc project) {
        String blockName = tr.td[0].text().trim()
        gradlebuild.docs.dsl.docbook.model.BlockDoc blockDoc = project.getBlock(blockName)
        tr.children = {

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-test</groupId>
  <artifactId>t05-a</artifactId>
  <packaging>jar</packaging>
  <version>2.0</version>
  <repositories>
    <repository>
      <id>central</id>
      <name>Fake Maven Central Repository</name>
      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>

# Generate the API docs
./gradlew dokkaHtmlMultiModule

mv ./build/dokka/htmlMultiModule docs/4.x

# Copy in special files that GitHub wants in the project root.
cat README.md | grep -v 'project website' > docs/index.md
cp CHANGELOG.md docs/changelogs/changelog.md
cp CONTRIBUTING.md docs/contribute/contributing.md

# Build the site locally

Most of these ideas would be more or less **independent**, and in most cases you should only need to study them if they apply directly to **your project**.

If something seems interesting and useful to your project, go ahead and check it, but otherwise, you might probably just skip them.

/// tip

    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"
    feature: support "project.directory" property, ressembling future model addition of "directory" element along "artifactId"
  </description>

  <properties>
    <project.directory>child</project.directory>
  </properties>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <configuration>
          <tasks><echo>${project.parent.basedir}</echo></tasks>
        </configuration>
      </plugin>
    </plugins>
  </build>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <configuration>
          <tasks><echo>${project.parent.basedir}</echo></tasks>
        </configuration>
      </plugin>
    </plugins>
  </build>