typelevel / typelevel/sbt-typelevel
Java 8 in CI: the end is nigh
Open
Nobody has claimed this yet.
- #243 by @armanbilge — closed without merging
question
- Dominant language
- Scala
- Stars
- 185
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Maybe not tomorrow or even this year, but this stuckfast position will gradually grow more and more uncomfortable. E.g. our sbt-plugins are itching to leave us behind:
FWIW we can probably get along just fine without JDK 8 in CI. But perhaps I haven't heard the horror stories 😆
- The
tlJdkRelease := Some(8)setting activates all the scalac and javac flags to safely build/release from a newer JDK. - fs2 only runs CI on JDK 17 and besides the occasional bump is really a success story. Note that the
tlJdkReleasesetting would actually prevent thoseByteBuffer-oopsies. In fact fs2 can't use thetlJdkReleasesetting because it blocks access to JDK 9+ APIs!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the CI configuration and the tlJdkRelease := Some(8) setting described in the issue, then review the linked sbt-plugin compatibility concern. Determine which supported JDK versions the build and release process require; done means the CI policy is updated consistently and the affected builds still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100