https://github.com/osmerion/jvm-launcher
Tools to build a customized launcher executables for seamless experiences with JVM-based desktop applications.
https://github.com/osmerion/jvm-launcher
desktop-application java jvm launcher packaging
Last synced: 3 months ago
JSON representation
Tools to build a customized launcher executables for seamless experiences with JVM-based desktop applications.
- Host: GitHub
- URL: https://github.com/osmerion/jvm-launcher
- Owner: Osmerion
- License: apache-2.0
- Created: 2022-02-10T21:18:42.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2026-04-20T11:59:26.000Z (3 months ago)
- Last Synced: 2026-04-20T13:50:19.635Z (3 months ago)
- Topics: desktop-application, java, jvm, launcher, packaging
- Language: Kotlin
- Homepage:
- Size: 528 KB
- Stars: 4
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
README
# jvm-launcher
[](https://github.com/Osmerion/jvm-launcher/blob/master/LICENSE)
Tools to build a customized launcher executables for seamless experiences with
JVM-based desktop applications.
## Why?
Although Window icons and titles can be changed easily using common GUI
libraries, many Java desktop application use the JVM's native launchers
(`java.exe` or `javaw.exe`) to start the application. Neither of them are
customizable which leads to a poor user experience when interacting with the
application through the task manager and other system tools.
## How?
This project implements a custom Java launcher using the JNI invocation API to
launch a JVM. The launcher is small and can easily be compiled with custom
resources to provide a seamless experience for end-users.
The launcher executable looks up a configuration file (`config.toml`) in its
parent directory to determine all necessary information to start the JVM. A
configuration file looks as follows:
```toml
libjvm_path = "./path/to/jvm.dll"
main_class = "com/example/Main"
jvm_args = [
"-Djava.class.path=;"
]
```
## Usage
[Learn how to use the Gradle plugin](/integrations/gradle/README.md) to
integrate building a custom launcher into an application's build process.
## Building from source
### Setup
This project uses [Gradle's toolchain support](https://docs.gradle.org/current/userguide/toolchains.html)
to detect and select the JDKs required to run the build. Please refer to the
build scripts to find out which toolchains are requested.
An installed JDK 17 (or later) is required to use Gradle.
### Building
Once the setup is complete, invoke the respective Gradle tasks using the
following command on Unix/macOS:
./gradlew
or the following command on Windows:
gradlew
Important Gradle tasks to remember are:
- `clean` - clean build results
- `build` - assemble and test the Java library
- `publishToMavenLocal` - build and install all public artifacts to the
local maven repository
Additionally `tasks` may be used to print a list of all available tasks.
## License
```
Copyright 2022-2025 Leon Linhart
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
```