You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JavaPackager is a hybrid plugin for **Maven** and **Gradle** which provides an easy way to package Java applications in native Windows, MacOS or GNU/Linux executables, and generate installers for them.
7
7
8
-
> SNAPSHOT version (available in `devel` branch) is not released to Maven Central, so you have to [install it manually](#how-to-build-and-install-the-plugin).
9
-
10
8
> :eyes: See [JavaPackager changes and fixes](https://github.com/fvarrui/JavaPackager/releases).
11
9
12
10
## History
@@ -123,21 +121,21 @@ gradle packageMyApp
123
121
124
122
By default it will generate next artifacts in `${outputDirectory} ` folder:
|`${name}`| Directory with native application and other assets. | All ||
127
+
|`${name}-${version}-runnable.jar`| Runnable JAR file. | All ||
128
+
|`${name}_${version}.AppImage`| AppImage package file. | GNU/Linux |[FUSE 2](https://github.com/AppImage/AppImageKit/wiki/FUSE) to run the app. |
129
+
|`${name}_${version}.deb`| DEB package file. | All ||
130
+
|`${name}_${version}.rpm`| RPM package file. | All ||
131
+
|`${name}_${version}.exe`| Setup file. | Windows |[Inno Setup](http://www.jrsoftware.org/isinfo.php) (`iscc` command must be in PATH variable)|
132
+
|`${name}_${version}.msi`| MSI installer file. | Windows |[WiX Toolset](https://wixtoolset.org/) (`candle` and `light` commands must be in PATH variable)|
133
+
|`${name}_${version}.msm`| MSI merge module file. | Windows |[WiX Toolset](https://wixtoolset.org/) ( `candle` and `light` commands must be in PATH variable)|
134
+
|`${name}_${version}.dmg`| Disk image file (uses **hdiutil**). | MacOS ||
|`${name}-${version}-${platform}.zip`| Zipball containing generated directory `${name}`. | All ||
137
+
|`${name}-${version}-${platform}.tar.gz`| Compressed tarball containing generated directory `${name}`. | All ||
138
+
|`assets`| Directory with all intermediate files generated by JavaPackager. | All ||
141
139
142
140
> **Inno Setup** and **WiX Toolset** installation [guide](docs/windows-tools-guide.md).
143
141
@@ -148,6 +146,7 @@ By default it will generate next artifacts in `${outputDirectory} ` folder:
148
146
|`additionalModulePaths`|:x:|`[]`| Additional module paths for `jdeps`. |
149
147
|`additionalModules`|:x:|`[]`| Additional modules to the ones identified by `jdeps` or the specified with `modules` property. |
150
148
|`additionalResources`|:x:|`[]`| Additional files and folders to include in the bundled app. |
149
+
|`arch`|:x:|`${os.arch}`| The dependency of some ArtifactGenerator objects in the process of making packages, such as GenerateDeb |
151
150
|`administratorRequired`|:x:|`false`| App will run as administrator (with elevated privileges). |
152
151
|`assetsDir`|:x:|`${basedir}/assets` or `${projectdir}/assets`| Assets location (icons and custom Velocity templates). |
153
152
|`bundleJre`|:x:|`false`| Embeds a customized JRE with the app. |
@@ -261,7 +260,7 @@ You can use [default templates](https://github.com/fvarrui/JavaPackager/tree/mas
261
260
262
261
### Additional JVM options at runtime
263
262
264
-
When you build your app, all configuration details are hardcoded into the executable and cannot be changed without recreating it or hacking with a resource editor. JavaPackager introduces a feature that allows to pass additional JVM options at runtime from an `.l4j.ini` file (like [Launch4j](http://launch4j.sourceforge.net/docs.html) does, but available for all platforms in the same way). So, you can specify these options in the packager's configuration (packaging time), in INI file (runtime) or in both.
263
+
When you build your app, all configuration details are hardcoded into the executable and cannot be changed without recreating or hacking it with a resource editor. JavaPackager introduces a feature that allows to pass additional JVM options at runtime from an `.l4j.ini` file (like [Launch4j](http://launch4j.sourceforge.net/docs.html) does, but available for all platforms in the same way). So, you can specify these options in the packager's configuration (packaging time), in INI file (runtime) or in both.
265
264
266
265
The INI file's name must correspond to `${name}.l4j.ini` and it has to be located next to the executable on Windows and GNU/Linux, and in `Resources` folder on MacOS.
267
266
@@ -389,9 +388,3 @@ Run next command (ommit `./` on Windows):
389
388
```bash
390
389
./gradlew publish closeAndReleaseRepository
391
390
```
392
-
393
-
> Related [guide](https://nemerosa.ghost.io/2015/07/01/publishing-to-the-maven-central-using-gradle/).
394
-
395
-
## Future features
396
-
397
-
Check the [TO-DO list](https://github.com/fvarrui/JavaPackager/projects/1#column-7704117) to know the features we plan to add to JavaPackager.
description ='Hybrid Maven/Gradle plugin to package Java applications as native Windows, Mac OS X or GNU/Linux executables and create installers for them'
0 commit comments