Releases: javapackager/JavaPackager
Releases · javapackager/JavaPackager
v0.9.3
v0.9.1
v0.9.0
- Published on Maven Central.
- Possibility to perform multiple executions.
v0.8.9
v0.8.8
- Added properties
runnableJar
andcopyDependencies
to allow use of your own jar (fixed #12).
<runnableJar>true|false</runnableJar>
<copyDependencies>true|false</copyDependencies>
- Added property
platform
to allow packaging for different OS than host (fixed #13).
<platform>auto|linux|mac|windows</platform>
- Added property
vmArgs
to allow custom VM arguments (e.g. -Xmx4G) (fixed #14).
<vmArgs>
<param>-Xmx4G</param>
</vmArgs>
- Added property
envPath
to allow setting PATH environment variable in GNU/Linux and MacOs startup scripts.
<envPath>/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin</envPath>
- Fixed error when determining module dependencies on MacOS and GNU/Linux, due to library files specified as
*.jar
were not being expanded when calling jdeps. - Also, now it's possible to use your own Velocity templates to customize some generated artifacts (startup, startup.sh, iss file, ...)
v0.8.7
- Fixed #11:
codesign
error on MacOS
- Config options removed (deprecated) because are no longer necessary:
forceJreOptimization
: it has been replaced forcustomizedJre
moduleDependenceAnalysisOption
: now the right option is choosed by the plugin, depending on JDK version
- Module depedence analysis fixed and enhanced.
v0.8.6
v0.8.5
- Fixed #8: Added parameter for specifying a different Module Dependence Analysis Option other than the default (--list- deps)
- Fixed #9: Added parameter for specifying additional modules than the ones calculated by jdeps before calling jlink
- Fixed #7: a problem when inside libs folder there are other artifacts beside jars (ie: wars)