Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install launch4j

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install launch4j

MacPorts ports tree · java/launch4j/Portfile · Quelle: api.github.com

Überblick

Paketzusammenfassung

Cross-platform Java executable wrapper

Projektlinks

Befehle und Aliase

launch4j

Verlauf

Projektgeschichte und Nutzung

Launch4j is a cross-platform build utility for wrapping Java applications in lightweight Windows native executables. It combines a GUI, command-line usage, Ant integration, Maven-oriented packaging, JRE discovery, version metadata, splash screens, manifests, and optional bundled-runtime behavior.

Projektgeschichte

The SourceForge project was registered on 2003-11-27 and is maintained under Grzegorz Kowal's SourceForge account. Its changelog shows a long-lived Java desktop tooling project: the 1.x line was active by 2004, version 2.0 beta1 on 2005-05-13 introduced a new cross-platform wrapper and XML configuration, and version 3.0.0 on 2008-03-16 added runtime and Windows integration improvements.

Later releases tracked Java and Windows ecosystem changes. Version 3.8 on 2015-05-09 Mavenized the project; version 3.11 on 2017-06-27 added basic Java 9 support and Linux 64-bit binaries; version 3.14 on 2021-03-07 switched to Java 1.8 and FlatLaf; version 3.50 on 2022-11-13 simplified runtime-search configuration.

Adoptionsgeschichte

Launch4j became a standard answer for Java developers who wanted a Windows .exe without abandoning cross-platform build machines. SourceForge lists operating-system support across Linux, Mac, Solaris, Windows, BSD, and ChromeOS for the tool itself, while noting that the wrapped program runs on Windows.

Homebrew and MacPorts packaging placed Launch4j into Unix-like developer workflows, especially for developers building Windows deliverables from macOS or Linux.

Wie es verwendet wird

A developer supplies a Launch4j XML configuration describing the jar or class entry point, icon, JRE constraints, command-line behavior, version information, and other wrapper settings. Launch4j then emits a Windows executable while the build can run from Windows, Linux, or macOS.

Warum Paket-Nerds sich dafür interessieren

Launch4j is package-nerd-significant because it is a bridge artifact: a Java program packaged on Unix-like systems whose main output is a Windows executable wrapper. It exercises packaging assumptions around GUI tools, command-line tools, Ant/Maven integration, MinGW-built headers, bundled runtimes, and platform-specific outputs.

Zeitleiste

2003: SourceForge project registered on 2003-11-27.
2004: Changelog includes version 1.3.1 dated 2004-11-05.
2005: Version 2.0 beta1 introduced a cross-platform wrapper and XML configuration.
2008: Version 3.0.0 added dynamic heap values and Windows integration fixes.
2015: Version 3.8 Mavenized Launch4j.
2017: Version 3.11 added basic Java 9 support and Linux 64-bit binaries.
2021: Version 3.14 switched dependencies to Java 1.8 and FlatLaf.
2022: Version 3.50 changed runtime path-search behavior.

Related projects

Related technologies include Java, Windows PE executables, MinGW, Ant, Maven, Sign4j, bundled JRE workflows, and platform-specific Java launchers.

Quellen

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für launch4j wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 5 Plattformziele verfügbar.
Installiert mit 1 Laufzeitabhängigkeiten.
Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`launch4j`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version3.50

Manager aktualisiert

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://launch4j.sourceforge.net/

InfoNo package-manager update timestamp was available.niedrig Konfidenz
InfoRelease/tag comparison is only available for GitHub repositories.https://launch4j.sourceforge.net/none Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:launch4j
Version	3.50
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/launch4j
Homepage	https://launch4j.sourceforge.net/
Repository	https://sourceforge.net/p/launch4j/git/ci/master/tree
Upstream-Dokumentation	https://launch4j.sourceforge.net/docs.html
Lizenz	BSD-3-Clause AND MIT
Quellarchiv	https://git.code.sf.net/p/launch4j/git.git
Abhängigkeiten	openjdk
Build-Abhängigkeiten	ant
Bottle	verfügbar (auf big_sur, catalina, monterey, sonoma, ventura)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	launch4j
Version Scheme	0
Revision	0
Requirements	arch macos
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	yes
Disabled	no
Keg Only	no
URL Keys	stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

MacPorts95%

launch4j

sudo port install launch4j

normalized package name match
Abgeglichen nach: Launch4j

MacPorts ports tree · api.github.com · MacPorts ports tree: java/launch4j/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Combined YAML source

View the package source record on GitHub.

combined/launch4j.yml

Verwendete Quellen

Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

launch4j mit Homebrew, MacPorts installieren