Setting Up a Java Development Environment

This tutorial shows how to prepare your local machine for Java development, including developing Java apps that run on Google Cloud. Follow these steps to install Java and relevant tools.


  • Install a JDK (Java Development Kit).
  • Install a build automation tool.
  • Install the gcloud CLI.
  • (Optional) Install an IDE or editor.
  • (Optional) Install IDE Google Cloud plugin.
  • Install the Cloud Client Libraries for Java.
  • Set up authentication.

Install a JDK (Java Development Kit)

You may choose any Java distribution of your choice by ensuring that the following environment variables are set:

  • JAVA_HOME: Points to the base of the JDK installation.
  • PATH: Includes $JAVA_HOME/bin.

Eclipse Temurin is the recommended OpenJDK (Java Development Kit) distribution for use with Google Cloud. Temurin is open-source licensed, Java SE TCK-certified, and tested to ensure production-quality performance and security.

Temurin's installation instructions vary by operating system.

If you are using Compute Engine boot images, you can use the following installation scripts.


  1. Determine the major version of CentOS/RHEL/Rocky Linux:
    eval "$(grep VERSION_ID /etc/os-release)"
    eval "$(grep ^ID= /etc/os-release)"
    read -ra split_version <<< "$VERSION_ID"
  2. Create the Adoptium source repo file, `/etc/yum.repos.d/adoptium.repo`:
    sudo tee /etc/yum.repos.d/adoptium.repo << EOM
  3. Update package lists:
    sudo yum update -y
  4. Install Temurin:
    sudo yum install -y temurin-17-jdk
  5. Verify installation:
    java -version


  1. Install the public repo GPG key. If you are using Ubuntu 16.4, pass the key through gpg --dearmor before saving to file. (ex: sudo wget ... | gpg --dearmor | sudo tee ...)
    sudo mkdir -p /etc/apt/keyrings
    sudo wget -O - |
      sudo tee /etc/apt/keyrings/adoptium.asc
  2. Determine the name of the Linux distribution, and create the source list file, /etc/apt/sources.list.d/adoptium.list:
    eval "$(grep VERSION_CODENAME /etc/os-release)"
    sudo tee /etc/apt/sources.list.d/adoptium.list << EOM
    deb [signed-by=/etc/apt/keyrings/adoptium.asc] $VERSION_CODENAME main
  3. Update package lists:
    sudo apt update -y
  4. Install Temurin:
    sudo apt install -y temurin-17-jdk
  5. Verify installation:
    java -version


  1. Determine the major version of SLES:
    eval "$(grep VERSION_ID /etc/os-release)"
    read -ra split_version <<< "$VERSION_ID"
  2. Install the public repository GPG key:
    sudo mkdir -p /etc/zypp/keyrings
    sudo wget -O - |
      sudo tee /etc/zypp/keyrings/adoptium.asc
    sudo rpm --import /etc/zypp/keyrings/adoptium.asc
  3. Determine the version of SLES, and register the Adoptium repository:
    sudo zypper ar -f "$MAJOR_VERSION/$(uname -m)" adoptium
  4. Update package lists:
    sudo zypper update -y
  5. Install Temurin:
    sudo zypper install -y temurin-17-jdk
  6. Verify installation:
    java -version


To install Temurin, run PowerShell version 3.0 or higher as an administrator with the following commands.

  1. Download Temurin. The Invoke-WebRequest command in the instructions below requires PowerShell 3.0 or newer.
    $JdkVersion = 17
    $JdkUrl = "$JdkVersion/ga/windows/x64/jdk/hotspot/normal/eclipse?project=jdk"
    $JdkExtractionPath = "C:\temurin-$JdkVersion-jdk"
    $JdkDownload = "$"
    [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]'Tls12'
    Invoke-WebRequest -Uri $JdkUrl -OutFile $JdkDownload
    Expand-Archive $JdkDownload -DestinationPath $JdkExtractionPath -Force
  2. Set the JAVA_HOME and Path variables:
    pushd $JdkExtractionPath
    $JdkPath = (Get-ChildItem).FullName
    [System.Environment]::SetEnvironmentVariable('JAVA_HOME', $JdkPath, 'Machine')
  3. (Optional) Refresh your session's `$env:Path` value. Otherwise, start a new session:
    $MachinePath = [System.Environment]::GetEnvironmentVariable('Path', 'Machine')
    $UserPath = [System.Environment]::GetEnvironmentVariable('Path', 'User')
    $env:Path = "$MachinePath;$UserPath"
  4. Verify installation:
    java -version

Install a build automation tool

Apache Maven, Gradle, and SBT are package management options that can help build Java app dependencies quickly and consistently across platforms.

Install the gcloud CLI

The gcloud CLI is a set of tools for Google Cloud. It contains gcloud, gsutil, and bq, which you can use to access Compute Engine, Cloud Storage, BigQuery, and other products and services from the command line. You can run these tools interactively or in your automated scripts.

(Optional) Install an IDE or editor

Popular editors (in no particular order) used to develop Java apps include, but are not limited to:

These editors (sometimes with the help of plugins) give you everything from syntax highlighting, intelli-sense, and code completion to fully integrated debugging capabilities.

(Optional) Install an IDE plugin

For access to helpful functions within your editor, check out the following plugins:

Install the Cloud Client Libraries for Java

Use the Cloud Client Libraries for Java to integrate with Google Cloud services, such as Datastore and Cloud Storage. You can install the package for an individual API, such as BigQuery, as shown in the following example.

If you are using Maven, add the following to your pom.xml file. For more information about BOMs, see The Google Cloud Platform Libraries BOM.

<!--  Using libraries-bom to manage versions.
See -->


If you are using Gradle, add the following to your dependencies:

implementation platform('')

implementation ''

If you are using sbt, add the following to your dependencies:

libraryDependencies += "" % "google-cloud-bigquery" % "2.40.2"

If you're using Visual Studio Code, IntelliJ, or Eclipse, you can add client libraries to your project using the following IDE plugins:

The plugins provide additional functionality, such as key management for service accounts. Refer to each plugin's documentation for details.

Set up authentication

To run the client library, you must first set up authentication.

Create local authentication credentials for your Google Account:

gcloud auth application-default login

For more information, see Authenticate for using client libraries.

Use the client library

// Imports the Google Cloud client library

public class QuickstartSample {
  public static void main(String... args) throws Exception {
    // Instantiate a client. If you don't specify credentials when constructing a client, the
    // client library will look for credentials in the environment, such as the
    // GOOGLE_APPLICATION_CREDENTIALS environment variable.
    BigQuery bigquery = BigQueryOptions.getDefaultInstance().getService();

    // The name for the new dataset
    String datasetName = "my_new_dataset";

    // Prepares a new dataset
    Dataset dataset = null;
    DatasetInfo datasetInfo = DatasetInfo.newBuilder(datasetName).build();

    // Creates the dataset
    dataset = bigquery.create(datasetInfo);

    System.out.printf("Dataset %s created.%n", dataset.getDatasetId().getDataset());

Configure endpoints for the client library

If you use APIs that support regional endpoints, use endpoints to configure which server to send requests to. For example, with the Google.Cloud.Dataproc.V1 API, you might configure a client endpoint. You can read more about regional endpoints for Dataproc here. Be sure to replace MY-PROJECT with your project name and us-central1 with the region appropriate for your configuration in the following example:

ClusterControllerSettings settings =
 try (ClusterControllerClient clusterControllerClient = ClusterControllerClient.create(settings)) {
   String projectId = "MY-PROJECT";
   String region = "us-central1";
   Cluster cluster = Cluster.newBuilder().build();

What's next

(Optional) Use the Maven or Gradle plugin for App Engine

If you are developing in the App Engine standard or flexible environment, you can use plugins for both Apache Maven and Gradle build tools that provide convenient functions for developing, testing, and deploying your apps directly.

For App Engine standard environments

Use the Maven App Engine plugin or Gradle plugin for App Engine standard environments.

For App Engine flexible environments

Use the Maven App Engine plugin or Gradle plugin for App Engine flexible environments.

More resources