Dependency Scanning and License Scanning Java 21 SBT Support

Release notes

Dependency Scanning and License Scanning will be able to support SBT projects using Java 21, which is due to be released on 19th September 2023.

Problem to solve

As a user, I want to specify Java version 21, so that I can use the most recent version of Java with Dependency Scanning and License Scanning with my SBT project.

Intended users

• Sasha (Software Developer)
• Cameron (Compliance Manager)

User experience goal

The user should be able to set the DS_JAVA_VERSION environment variable in their .gitlab-ci.yml to 21 and Java 21 should be used for their SBT project.

Proposal

We are going to add version of SBT that supports Java 21 to the Dependency Scanning Docker image once this version of SBT has been released.

Further details

The scope of this issue is limited to our Debian, non-FIPS image, because we anticipate that Redhat will be 1-2 months behind the official Java release schedule.

Documentation

• Document SBT support for Java 21 projects
• Remove documentation that Java 21 only supports Maven projects

Availability & Testing

Adding a new version of Java could result in different behaviour. We can increase confidence by extending our test capability as follows:

• The spec/gemnasium-maven_image_spec.rb integration test should be updated

Available Tier

• Ultimate

Implementation Plan

• Update GitLab documentation:
  • Update Supported languages and package managers to include a version of SBT that supports Java 21
• Update Gemnasium analyzer:
  • Update .tool-versions to include a version of SBT that supports Java 21
  • Automatically switch to correct version of SBT when a customer sets DS_JAVA_VERSION: 21
  • Add Java 21 SBT test in spec/gemnasium-maven_image_spec.rb

---

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.