MicroShed/microshed-testing

Upgrade to Java 17

Open

#401 opened on Dec 13, 2023

View on GitHubContributor guide
 (5 comments) (0 reactions) (1 assignee)Java (25 forks)auto 404
good first issueis:housekeeping

Repository metrics

Stars
 (68 stars)
PR merge metrics
 (PR metrics pending)

Description

We should upgrade to building and testing using Java 17 as a stepping stone to Java 21 (Necessary for Jakarta EE 11).

  • If necessary upgrade gradle wrapper
  • Update build.gradle (source/target compatibility)
  • Update pom.xml within sample-apps/ (source/target compatibility)
  • Update CI Workflow to build and run using Java 17
  • Update documentation

Contributor guide

Research direction
Inspect the current build configuration (build.gradle, pom.xml) and CI workflow to understand how Java version is set, then update to Java 17 accordingly, and update documentation.
Tech stack
javagithub actions
Domain
backendtestingbuild system
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaGradleMaven
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75