JetBrains Fleet 1.13 Help

Getting started with Kotlin

This tutorial gets you up to speed with Java development in JetBrains Fleet. It covers the installation, project setup, and working with code. In order to complete it, you need JetBrains Toolbox 1.22.10970 or later: the Download page.

Download and install Fleet

  1. Make sure you are logged in JetBrains Toolbox under your JetBrains Account.

  2. In JetBrains Toolbox, click Install near the JetBrains Fleet icon.

    Download and install Fleet

Set up a workspace

Workspace is the directory where your project resides. It contains the project files and settings. You can open an existing project or start a new project by opening an empty directory.

In this tutorial, we will start a new project and have it initialized by Gradle.

Open a workspace

  1. From the File menu, select Open ⌘O.

  2. In the file browser, navigate to an empty folder where you want to store your code and click Open.

When you open a directory, it becomes the root of a workspace. You can view its contents in the Files view.

The Files view in the left panel

Now let's initialize the project. This will generate the boilerplate and some example code that we can use to try out Fleet in action. The steps differ depending on the build system. Use the tabs below to see the steps for a particular build system.

Initialize the project

  1. Make sure Gradle is installed on your computer.

  2. Press ⌘⌥T to open a terminal and execute the gradle init command.

  3. When prompted, answer:

    • Project type – 2 (application)

    • Implementation language – 4 (Kotlin)

    • Split functionality across subprojects – 1 (no)

    • Build script DSL – 2 (Kotlin)

    • Generate build using new APIs and behavior – no

    • Project name – skip

    • Source package – skip

By default, Fleet uses the JDK from your JAVA_HOME environment variable. Before proceeding, make sure it is configured in your environment. Otherwise, you can configure a custom JDK for your project.

Configure project JDK

  1. Open Settings/Preferences ⌘,.

  2. Select one of the available JDKs in the JDK menu. If no JDK is detected, you can add it manually by specifying the path to the required JDK.

    Java Runtime section in project settings

Smart mode

You can use JetBrains Fleet as a smart text editor, rather than a full-fledged IDE. However, if you need code intelligence features, you can enable them by turning the Smart Mode on.

Enable smart mode

  • In the top-right corner of the window, click Smart Mode, then Enable.

    After you click the Enable button, you may have to wait for some time, while the backend is being prepared.

    Smart mode popup

Here's what you can do in Smart Mode. The below is not an exhaustive list of Smart Mode features, rather a couple of examples that'll help you to get the feel of how it works in Fleet.

Use quick-fixes and intention actions

  • Press ⌥↵ to access actions that Fleet suggests in the current context.

    A popup shows the available fixes for the code at the caret

Refactor code

  • Place the caret at a literal or select an expression, then press ⌘⌥V.

    Choosing a new name for the symbol at the caret

    A variable is extracted from the selection.

  • Navigate to the declaration of a symbol with ⌘B.

  • Use inlay hints navigate to usages and hierarchy members.

    An interline shows the usages count for a symbol
  • Skim over the errors with ⌘E and ⌘⇧E

Use live templates

  • To generate a for loop, type iter and press . Press as you fill in the necessary variables.

    Populating the for loop template

Run and debug

With Smart Mode enabled, you can run your project. For that, you can use a gutter icon in the editor, or you can create a run configuration that will allow you to fine-tune the way your application should be run.

Run from the editor

  • Navigate to the entry point of your application and click the run icon in the gutter. Select Run.

    A popup appears upon clicking the gutter icon asking whether we want to run or debug the application

As mentioned before, another way to run a program is to use a run configuration. It allows you to customize the startup: add arguments, VM options, use custom commands, and so on.

Create a run configuration

  1. Press ⌘R. Run & Debug dialog opens.

    Create Run Configurations option in the Run and Debug popup

    Click Create Run Configurations.

  2. In run.json, append a gradle run configuration to the array, so that the resulting JSON looks like the following:

    { "configurations": [ { "name": "run sh", "type": "command", "program": "/bin/sh" }, { "name": "gradle run", "type": "gradle", "tasks": [ "run" ] } ] }

Launch a run configuration

  • Press ⌘R. The Run dialog opens. Select the newly created gradle run configuration.

    The application runs, and you can review its output in the console that opens.

    The task output is shown in the console

Debug the application

  1. Set a breakpoint by clicking at an executable line in the gutter. This will suspend the application just when this line is about to execute.

    A circle in the gutter indicating a breakpoint
  2. If you are going to launch the debug session using a run configuration, add "debugJvm": "true", to the run configuration you are using, so that it looks like the following:

    { "name": "gradle run", "debugJvm": "true", "type": "gradle", "tasks": [ "run" ] }
  3. Run the application by selecting Debug from the gutter menu or launching a previously saved run configuration.

    A highlighted line indicates the execution point
  4. Inspect the program state in the Run and debug panel. As we are using a hello-world type of app here, we don't have a lot of state to inspect.

    The buttons above the threads list let you control the program execution. You can advance it line-by-line, step in and out of methods, resume and stop the program.

    Threads are shown in the Debug panel
Last modified: 28 October 2022