Skip to content
This repository has been archived by the owner on Jan 14, 2024. It is now read-only.

Use JDK 16 #18

Closed
PascalHonegger opened this issue Mar 17, 2021 · 1 comment · Fixed by #66
Closed

Use JDK 16 #18

PascalHonegger opened this issue Mar 17, 2021 · 1 comment · Fixed by #66
Assignees
Labels
prio:should Should be implemented if feasible type:ci Working on Continous Integration, builds, dependency upgrades and such

Comments

@PascalHonegger
Copy link
Owner

Given the release of JDK 16, it would be nice to both use JDK 16 during development and as a runtime within docker.
Given how new JDK 16 is, we might need to wait until the necessary docker images are created.

@PascalHonegger PascalHonegger added prio:should Should be implemented if feasible type:ci Working on Continous Integration, builds, dependency upgrades and such labels Mar 18, 2021
@PascalHonegger PascalHonegger added this to To do in ChaosConnect Mar 18, 2021
@PascalHonegger PascalHonegger moved this from To do to Backlog in ChaosConnect Mar 18, 2021
@mjossdev mjossdev self-assigned this Mar 20, 2021
@mjossdev mjossdev moved this from Backlog to To do in ChaosConnect Mar 20, 2021
@PascalHonegger PascalHonegger modified the milestone: Week 07 Apr 4, 2021
@PascalHonegger
Copy link
Owner Author

Depends on johnrengelman/shadow#658

Depends on Kotlin 1.5.0 Release

@PascalHonegger PascalHonegger moved this from To do to In progress in ChaosConnect May 12, 2021
@PascalHonegger PascalHonegger linked a pull request May 12, 2021 that will close this issue
ChaosConnect automation moved this from In progress to Done May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
prio:should Should be implemented if feasible type:ci Working on Continous Integration, builds, dependency upgrades and such
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants