sbt/sbt-native-packager

Support for jpackage of JDK 16

Open

#1,405 opened on Mar 16, 2021

View on GitHub
 (1 comment) (7 reactions) (0 assignees)Scala (1,593 stars) (439 forks)batch import
feature requesthelp wantedjdkpackager

Description

JDK 16 brings with it a new packaging tool jpackage.

Although it seems like a competitor to a degree, it would make sense to make it available through sbt-native-packager as this one includes a JDK in the final distribution and targets Desktop applications it seems; and of course abstracting it away improves things for the end users :-)

Contributor guide

Tech stack
scalajava
Domain
releasedesktop
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Scalasbt build toolJava packagingJDK 16 jpackage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the jpackage tool provided in JDK 16, focusing on its command line interface and configuration options. Review existing sbt native packager plugins (e.g., JlinkPlugin, DockerPlugin) to understand the pattern for integrating new packaging formats. Look at the issue comments and the repository's contributing guidelines. Then propose a design for a new JpackagePlugin, considering how to map sbt settings to jpackage arguments. The main challenge is abstracting jpackage's features while staying consistent with the plugin's architecture.