Skip to content

Latest commit

 

History

History
67 lines (46 loc) · 2.57 KB

File metadata and controls

67 lines (46 loc) · 2.57 KB

Practical 1 : Get the workshop project and open it on IntelliJ

Fork & clone the project on GitHub

Follow the instructions given in the practical 3 of the GitLab workshop, by replacing the project URL by : https://github.com/BIOP/intellij-workshop

Open the project on IntelliJ

  • Open IntelliJ.

Note: If you don't have it on your computer, please download and install the COMMUNITY edition from the official website.

  • On the Welcome window, select Open a project
  • Browse and select the project folder you've clone from GitLab (i.e. intelliJ-workshop-demo)

Quick overview of IntelliJ

JDK configuration

To be interpreted correctly (i.e. understand its commands), Java needs a JDK (Java Development Kit). This JDK contains all the required tools to understand and build a Java code. Of course, a JDK depends on the version of Java you are using, and you cannot have multiple JDKs configured for the same project.

For this workshop, you will use Fiji. To be stable, it needs Java 8.

Note : Recently, Fiji has been updated to be compatible with Java 21. This update is quite recent and not all the functionalities have already been tested under this new version of Java. Therefore, we'll stick to Java 8 version in this workshop.

  1. Click on File -> Project Structure and select Project tab.
  2. Under the SDK (standing for Software Development Kit) field, choose the JDK 1.8

Note: If you don't have the 1.8 version of the JDK,

  • Click on Add SDK -> Download JDK
  • Select the version to 1.8
  • Select the vendor Amazon Corretto => Other vendors are available ; feel free to choose anyone you prefer.
  • Click Download
  1. Under the Language level field, select 8 - Lambdas, type annotations etc
  2. Click on Ok

Note: The JDK configuration can take some time ; you can see its progression in the bottom right. During this operation, IntelliJ downloads the JDK and indexes java files with your code to understand it.