## Building and Testing

The most reliable way to build and test Guava is:

```shell
./mvnw clean install
```

If you want to run a single test, you'll need to pass multiple flags because
Guava is a multi-module project. For performance reasons, you may also wish to
skip generating Javadoc. For example:

```shell
./mvnw clean install -Dtest=FinalizableReferenceQueueTest -DfailIfNoTests=false -Dmaven.javadoc.skip
```

        name = "Start Release Cycle Test"
        description = "Test for Start Release Cycle pipeline"

        steps {
            gradleWrapper {
                name = "PromoteTest"
                tasks = "clean promoteStartReleaseCycle"
                useGradleWrapper = true
                gradleParams =

  private val x509TrustManagerExtensions: X509TrustManagerExtensions,
) : CertificateChainCleaner() {
  @Suppress("UNCHECKED_CAST")
  @Throws(SSLPeerUnverifiedException::class)
  @SuppressSignatureCheck
  override fun clean(
    chain: List<Certificate>,
    hostname: String,
  ): List<Certificate> {
    val certificates = (chain as List<X509Certificate>).toTypedArray()
    try {

        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          COMMIT_SHA: ${{ github.event.workflow_run.head_sha }}
          RUN_ID: ${{ github.run_id }}
          STATE: "pending"
      - name: Clean site
        run: |
          rm -rf ./site
          mkdir ./site
      - uses: actions/download-artifact@v8
        with:
          path: ./site/
          pattern: docs-site-*
          merge-multiple: true

# limitations under the License.
# ==============================================================================
#
# setup.packages.sh: Given a list of Ubuntu packages, install them and clean up.
# Usage: setup.packages.sh <package_list.txt>
set -e

# Prevent apt install tzinfo from asking our location (assumes UTC)
export DEBIAN_FRONTEND=noninteractive

apt-get update

 * based on include/exclude patterns. This service provides a clean API for plugins
 * to create path matchers without directly depending on implementation classes.
 * <p>
 * The path matchers created by this service support Maven's traditional include/exclude
 * pattern syntax, which is compatible with the behavior of Maven 3 plugins like
 * maven-compiler-plugin and maven-clean-plugin.
 * <p>
 * Pattern syntax supports:
 * <ul>

[Individual Contributor License Agreement (CLA)][cla].


Code Contributions
------------------

Get working code on a personal branch with tests passing before you submit a PR:

```
./gradlew clean check
```

Please make every effort to follow existing conventions and style in order to keep the code as
readable as possible.

[Individual Contributor License Agreement (CLA)][cla].


Code Contributions
------------------

Get working code on a personal branch with tests passing before you submit a PR:

```
./gradlew clean check
```

Please make every effort to follow existing conventions and style in order to keep the code as
readable as possible.

                       "PATH+MAVEN=${ tool "jdk_17_latest" }/bin:${tool "maven_3_latest"}/bin",
                       "MAVEN_OPTS=-Xms4G -Xmx4G -Djava.awt.headless=true"]) {
                sh "./mvnw clean deploy -DdeployAtEnd=true -B -V"
              }
            }
          }
        }
      }
    }
  }
}

boolean isDeployedBranch() {

        fun assertCorrectParameters(
            subProjectName: String,
            functionalTests: List<BaseGradleBuildType>,
        ) {
            functionalTests.forEach { assertTrue(it.getGradleTasks().startsWith("clean $subProjectName")) }
            if (functionalTests.size == 1) {
                assertFalse(functionalTests[0].getGradleParams().contains("-PincludeTestClasses"))