Project-aware input
InstallerLab starts from the .b4j project and reads supported #PackagerProperty values such as executable name, icon, version and included modules.
Turn a B4J project into a standalone Windows distribution, then package it for users.
InstallerLab v3's dedicated B4J Portable workflow reads packaging properties from your project, uses the B4J/JDK toolchain already configured on the developer machine, compiles through B4JBuilder and creates the standalone distribution needed for a real Windows package.
.b4j project#PackagerPropertyB4JBuilderB4JPackager11Standalone runtimeInstallerLab Launcher
Why this is different from simply pressing “Build Standalone Package” in B4J
Toolchain discovery
It can detect the local B4J installation and JDK configuration used by the developer, reducing manual path setup.
Compilation plus packaging
The flow coordinates B4JBuilder and B4JPackager11 rather than treating an already-built folder as an opaque application.
InstallerLab's launcher layer
The generated distribution adds InstallerLab's launcher/distribution layer on top of the runtime produced by the B4J toolchain.
Ready for the next distribution step
Once the B4J application is standalone, InstallerLab can place it into the broader Windows packaging workflow instead of leaving you with only a raw output folder.
End users do not need your development environment
A correctly generated standalone distribution carries the required runtime pieces so the target user does not need B4J or a separately installed global Java runtime.
Typical B4J packaging properties
#PackagerProperty: IconFile = ..\icon.ico
#PackagerProperty: ExeName = My Application.exe
#PackagerProperty: IncludedModules = jdk.crypto.ec, javafx.swing, javafx.web
#PackagerProperty: Version = 1.0.0What InstallerLab can extract
- Executable name.
- Application version.
- Icon file where configured.
- Included Java modules.
- Local toolchain information needed for the build.
A practical developer flow
| Step | What happens |
|---|---|
| 1. Select project | Choose the .b4j project you want to distribute. |
| 2. Inspect | InstallerLab reads supported packaging properties and validates the source information. |
| 3. Compile | The local B4J toolchain compiles the application. |
| 4. Build standalone runtime | B4JPackager11 prepares the self-contained distribution using the selected modules. |
| 5. Add InstallerLab layer | The resulting package is prepared for InstallerLab's portable/distribution workflow. |
| 6. Distribute | Use the output directly where appropriate or continue into InstallerLab's Windows installer workflow. |
B4J packaging FAQ
Does a normal InstallerLab user need B4J?
No. B4J is only needed when using the dedicated B4J Portable integration for a B4J project. Normal Application, Office Add-in and QGIS Plugin workflows are separate.
Does the end user need Java installed?
A correctly generated B4J standalone distribution includes its required runtime, so the user does not need to install a global Java runtime separately.
Why use InstallerLab if B4J already packages apps?
B4J provides the official compilation and runtime packaging toolchain. InstallerLab coordinates that toolchain, reads project properties and adds a broader distribution layer so the output can move into the same installer workflow used for other Windows apps.
Package the B4J application you are already building.
InstallerLab is written with B4J itself, so the B4J Portable workflow is designed around the toolchain B4J developers actually use rather than treating B4J as a generic Java application.