JarToExe 1.8 Jar2Exe is a tool to convert jar files into exe files. Following are the main features as describe on their website: Can generate “Console”, “Windows GUI”, “Windows Service” three types of.exe files. Generated.exe files can add program icons and version information.
- Convert Mac Files To Pc
- Convert Mac Files To Windows
- Convert .jar To .exe For Mac Pro
- Convert .jar To .exe For Mac Free
Note: we recommend to have a proper knowledge of OSX and Java. We’re not going to explain how to do certain things, because the article would be too long.
- A folder containing appbundler -1.0ea.jar. A dist folder with the jar file we want to convert. Optionally, a icns file that we have previously worked in and contains a whole family of icons with different sizes, to embellish the app file.
- How can I convert.exe to.jar?Nonsensical question. An executable (.exe) is binary code that the OS understands directly. A.jar is a Java Archive of bytecode for the Java VM to understand. Jeepers, man.
- How to Open Exe Files on Mac. This wikiHow teaches you how to run Windows' executable (EXE) files on a Mac. To do so, you can either install WINE, which is free software, or install Windows 8 or 10 using your Mac's Boot Camp feature.
One of the most difficult tasks while developing Crazy Belts has been setting the game to OSX. There is little information and very few tools to do it; in fact, only one tool available to pack a jar file into an app. This was a mandatory step to publish our game inside and outside OSX App Store. In Jemchicomac, we used two process for this:
- Gatekeeper: to publish outside the store
- Sandbox: to publish inside the store
Gatekeeper prevents third party apps to be run in the system without Apple’s signature and verification. It’s conceived for those apps that come from another stores or websites not related to the App Store. User can disable Gatekeeper, but we consider that’s fair to demonstrate you’re a valid partner of Apple and you app is trustworthy.
On the other hand, Sandbox is a tool that encapsulates you app and check it: if it’s harmful, then Sandbox aparts it from the rest of the operative system. This is an essential requirement to publish in the Mac Store and it has a different signature than Gatekeeper.
Before all of this, as you have imagined, it’s necessary to convert our jar in an app, whatever our commercial goal in OSX is. We need the following tools:
- App Bundler: https://bitbucket.org/infinitekind/appbundler, that’s going to convert our jar to app. You have to download it, compile and pack it with ant. You must do it in Mac, not Windows.
- JRE or JDK: you need Java in your computer. It doesn’t have to be Oracle’s Java Virtual Machine, but it’s the one we used.
- Mac Developer account: essential to sign the app.
Given those ingredients, we can start creating our app. We need Java 7 (in our OSX system, we find only Java 6 as preinstalled). Once we install our JVM with Java 7, we must go to one of the jdk or jre installations. For instance: …/home/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk. We click on the icon, and if the active version of Java is SE6 we have to disable it , and check SE7.
Now you have to configure Java Home: http://www.mkyong.com/java/how-to-set-java_home-environment-variable-on-mac-os-x/
Once all of this is done, we’re ready for the next step. We create a folder with all necessary thing to build our app (I called mine “build”).
- A build.xml file with the information for Ant of Java to create our app
- An empty info.plist file. We just create a file called this.
- A folder containing appbundler -1.0ea.jar.
- A dist folder with the jar file we want to convert.
- Optionally, a icns file that we have previously worked in and contains a whole family of icons with different sizes, to embellish the app file.
Before going on, we have to warn you that all this work is made with the Terminal and we have to go to each directory when required. For instance, if my build folder is at the Desktop, in the Terminal I must go using
[bash]cd desktop/build.[/bash]For me, build.xml is like this:
[xml]<?xml version='1.0' encoding='UTF-8'?><project name='CrazyBelts' default='default' basedir='.'>
<target name='bundle'>
<taskdef name='bundleapp'
classpath='lib/appbundler-1.0ea.jar'
classname='com.oracle.appbundler.AppBundlerTask'/>
<bundleapp
outputdirectory='dist'
name='Crazy Belts'
displayname='Crazy Belts'
identifier='com.company.crazybelts'
shortversion='1.3.0'
version='1.3.0'
icon='icon.icns'
mainclassname='org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader'
copyright='2014 Company'
applicationCategory='public.app-category.puzzle-games'>
<classpath file='dist/CrazyBelts12FINAL.jar'/>
<runtime/>
<!– Workaround since the icon parameter for bundleapp doesn’t work –>
<option value='-Xdock:icon=Contents/Resources/${bundle.icon}'/>
<arch name='x86_64'/>
<arch name='i386'/>
</bundleapp>
</target>
</project>[/xml]
Let’see each entry:
[xml]<project name='CrazyBelts' default='default' basedir='.'>[/xml]We must change the name to our app name.
[xml]<target name='bundle'>[/xml]This is the name of our Ant task, meaning this is the one we should use when calling for Ant. In our example, once we’re set in the directory we type:
[bash]ant bundle[/bash]Taskdef must match the label of the task we want to run. In classpath we type the directory where the AppBundler is located. Finally, we leave classname without changes.
[xml]<bundleappoutputdirectory='dist'
name='Crazy Belts'
displayname='Crazy Belts'
identifier='com.company.crazybelts'
shortversion='1.3.0'
version='1.3.0'
icon='icon.icns'
mainclassname='org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader'
copyright='2014 Company'
applicationCategory='public.app-category.puzzle-games'>[/xml]
The main block of build.xml:
- Output directory: we can put here the jar to pack (in our case, we did this), and it’ll also contain the app when it’s created.
- name: the name of the app
- display name: the name as displayed
- identifier: it must match an App ID registered in your Mac Developer account. This registration can be done afterwards, and it’s only necessary if you’re going to distribute in the Mac Store, not for third parties.
- Shortversion: the game version
- Icon: this is the icon we mentioned before, in the root of the build folder.
- Mainclassname: this is a very important entry. We must indicate the class that runs the app. In our case, we used Eclipse and we did spend so much time setting the main class of the app, while this IDE actually used his own Leader class when creating the exe jar.
- Copyright: our national copyright
- applicationCategory: our app category code. Visit this link to know more about it: https://developer.apple.com/library/Mac/releasenotes/General/SubmittingToMacAppStore/#//apple_ref/doc/uid/TP40010572-CH16-SW8
<!– Workaround since the icon parameter for bundleapp doesn’t work –>
<option value='-Xdock:icon=Contents/Resources/${bundle.icon}'/>
<arch name='x86_64'/>
<arch name='i386'/>[/xml]
Only runtime.dir is important for us, we don’t touch the rest. This entry is optional and if we don’t include it in our app it won’t have an embedded jdk. Good news are that doesn’t require much space; bad news are that if the user doesn’t have the correct jdk or jre, the app won’t run, so it’s poorly advisable. This includes the path where our jdk is located; if we don’t know it and we’re using Eclipse, we can go to Preferences and check the jre.
After that, we must go to the Terminal and type:
[bash]ant bundle.[/bash]A package with .app extension will be created, and it will contain our .jar
The final part is signing the app. In our example, we must use another way apart from Xcode. Everything will be done using Terminal.
We’re going to start with the Gatekeeper version, the easier one. To sign an app and be accepted by this technology we must create a certificate with a Team Agent account. Be very careful with this: to publish outside the App Store you must create a Developer ID Application Certificate or Developer ID Installer Certificate, depending on whether we want to only sign the app as it is or to pack it into an installer (that also has to be signed).
To create a certificate, we always have to go to the development console in the section “Certificates, Identifiers & Profiles”. Once created and added to the Keychain (check carefully we have the private key associated to the public one), we just set into the app directory and type:
[bash]codesign -v -f -s 'Developer ID Application' 'myapp.app'[/bash]If we get an error message, we type the following command: export CODESIGN_ALLOCATE=”/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate”
And if everything goes right, we must see this: signed bundle with Mach-O universal (i386 x86_64) [com.company.myapp]
You use the
javapackager
command to perform tasks related to packaging Java and JavaFX applications.Synopsis
command
The task that you want to perform. See Commands for the javapackager Command.
options
One or more options for the command, separated by spaces. See Options for the createbss Command, Options for the createjar Command, Options for the deploy Command, Options for the makeall Command, and Options for the signjar Command.
Note:
The
javapackager
command isn’t available on Oracle Solaris.Description
The Java Packager tool compiles, packages, and prepares Java and JavaFX applications for distribution. The
javapackager
command is the command-line version. For available Ant tasks, see JavaFX Ant Tasks in Java Platform, Standard Edition Deployment Guide.For self-contained applications, the Java Packager for JDK 9 packages applications with a JDK 9 runtime image generated by the
jlink
tool. To package a JDK 8 or JDK 7 JRE with your application, use the JDK 8 Java Packager.Commands for the javapackager Command
Delphi ds150e 2018 download. You can run the following commands from the command line, followed by the options for the command.
-createbss
Converts CSS files into binary form. See Options for the createbss Command for the options used with this command.
-createjar
Produces a JAR according to other parameters. See Options for the createjar Command for the options used with this command.
-deploy
Assembles the application package for distribution. Modular and nonmodular applications are supported. By default, the deploy task generates the base application package. It can also generate a self-contained application package, if requested. See Options for the deploy Command for the options used with this command.
The bundle for a self-contained application includes a custom runtime created by calling
jlink
. The Java Packager for JDK 9 packages applications with a JDK 9 runtime image. To package a JDK 8 or JDK 7 JRE with your application, use the JDK 8 Java Packager.-makeall
Note:
The -makeall
command for the Java Packager tool is deprecated in JDK 9 in preparation for removal in a future release.Performs compilation,
createjar
, and deploy
steps as one call, with most arguments predefined, and attempts to generate all applicable self-contained application packages. The source files must be located in a folder called src
, and the resulting files (JAR, JNLP, HTML, and self-contained application packages) are put in a folder called dist
. This command can be configured only in a minimal way and is as automated as possible. See Options for the makeall Command for the options used with this command.-signjar
Note:
The -signjar
command for the Java Packager tool is deprecated in JDK 9 in preparation for removal in a future release. It also doesn’t work with multirelease JAR file. Instead, use the jarsigner tool to sign the JAR file.Signs JAR files with a provided certificate. See Options for the signjar Command for the options used with this command.
Options for the createbss Command
-outdir dir
Name of the directory that receives the generated output files.
-srcdir dir
Base directory of the files to pack.
-srcfiles files
List of files in
srcdir
. If omitted, all files in srcdir
(which is a mandatory argument in this case) will be used.Options for the createjar Command
-appclass app-class
Qualified name of the application class to be executed.
-argument arg
An unnamed argument to be inserted into the JNLP file as an
<fx:argument>
60 seconds apocalypse game online play free. element.-classpath files
List of dependent JAR file names.
-manifestAttrs manifest-attributes
List of names and values for additional manifest attributes. Syntax:
-nocss2bin
The packager doesn’t convert CSS files to binary form before copying to JAR file.
-noembedlauncher
If present, the packager will not add the JavaFX launcher classes to the jarfile.
-outdir dir
Name of the directory that receives the generated output files.
-outfile filename
Name (without the extension) of the file that’s generated.
-paramfile file
Properties file with named parameters and their default values to pass to the application.
-preloader preloader-class
Qualified name of the JavaFX preloader class to be executed. Use this option only for JavaFX applications. Don’t use for Java applications, including headless applications.
-runtimeversion version
Specifies the version of the required JavaFX Runtime.
-srcdir dir
Base directory of the files to pack.
-srcfiles files
List of files in
srcdir
. If omitted, all files in srcdir
(which is a mandatory argument in this case) will be packed.Options for the deploy Command
--add-modules modulename[,modulename.]
Specifies the root modules to resolve in addition to the initial module.
-allpermissions
If present, the application requires all security permissions in the JNLP file.
-appclass app-class
Qualified name of the application class to be executed.
-argument arg
An unnamed argument to be inserted into an
<fx:argument>
element in the JNLP file.-Bbundler-argument=value
Provides information to the bundler that’s used to package a self-contained application. See Arguments for Self-Contained Application Bundles for information about the arguments for each bundler.
-callbacks callback-methods
Specifies one or more user callback methods in generated HTML. The format is the following:
-description description
Description of the application.
-embedjnlp
If present, the JNLP file embedded in the HTML document.
-embedCertificates
If present, the certificates will be embedded in the jnlp file.
-height height
Height of the application.
-htmlparamfile file
Properties file with parameters for the resulting application when it is run in the browser.
-isExtension
If present, the
srcfiles
as extensions.--limit-modules modulename[,modulename.]
Limits the universe of observable modules.
-m modulename [/mainclass]
or --module modulename [/mainclass]
Specifies the initial module to resolve, and the name of the main class to execute if not specified by the module.
-p module path
or --module-path module path
A : separated list of directories, each directory is a directory of modules.
-name name
Name of the application.
-native type
Generate the files needed for a Java Web Start application when
type
is set to jnlp
. Otherwise, generate self-contained application bundles, if possible. Use the -B
option to provide arguments to the bundlers being used. If type
is specified, then only a bundle of this type is created. If no type is specified, then all
is used.The following values are valid for type:
jnlp
: Generates the.jnlp
and.html
files for a Java Web Start application.all
: Runs all of the installers for the platform on which it’s running, and creates a disk image for the application. This value is used iftype
isn’t specified.installer
: Runs all of the installers for the platform on which it’s running.image
: Creates a disk image for the application.Linux and Windows: The image is the directory that gets installed.macOS: The image is the.app
file.exe
: Generates a Windows.exe
package.msi
: Generates a Windows Installer package.dmg
: Generates a DMG file for macOS.pkg
: Generates a.pkg
package for macOS.mac.appStore
: Generates a package for the Mac App Store.rpm
: Generates an RPM package for Linux.deb
: Generates a Debian package for Linux.
-nosign
Linux and macOS: If present, the bundle generated for self-contained applications isn’t signed by the bundler. The default for bundlers that support signing is to sign the bundle if signing keys are properly configured. This attribute is ignored by bundlers that don’t support signing.
-outdir dir
Name of the directory that receives the generated output files.
-outfile filename
Name (without the extension) of the file that is generated.
-paramfile file
Properties file with named parameters and their default values to pass to the application.
-preloader preloader-class
Qualified name of the JavaFX preloader class to be executed. Use this option only for JavaFX applications. Don’t use for Java applications, including headless applications.
-srcdir dir
Base directory of the files to pack.
-srcfiles files
List of files in
srcdir
. If omitted, all files in srcdir
(which is a mandatory argument in this case) will be used.--strip-native-commands [true|false]
Remove command-line tools such as
java.exe
from the Java runtime that’s generated for packaging with self-contained applications. The default is true
. To keep the tools in the runtime, specify false
.-templateId
Application ID of the application for template processing.
-templateInFilename
Name of the HTML template file. Placeholders are in the following form:
APPID
is the identifier of an application and XXXX
is one of following:DT.SCRIPT.URL
Location ofdtjava.js
in the Deployment Toolkit. By default, the location ishttp://java.com/js/dtjava.js
.DT.SCRIPT.CODE
Script element to includedtjava.js
of the Deployment Toolkit.DT.EMBED.CODE.DYNAMIC
Code to embed the application into a given placeholder. It is expected that the code is wrapped in thefunction()
method.DT.EMBED.CODE.ONLOAD
All of the code needed to embed the application into a web page using theonload
hook (except inclusion ofdtjava.js
).DT.LAUNCH.CODE
Code needed to launch the application. It’s expected that the code is wrapped in thefunction()
method.
-templateOutFilename
Name of the HTML file generated from the template.
-title title
Title of the application.
-updatemode update-mode
Sets the update mode for the JNLP file.
-vendor vendor
No limits coaster 2 free download. Vendor of the application.
-width width
Width of the application.
Options for the makeall Command
Convert Mac Files To Pc
Note:
The -makeall
command for the Java Packager tool is deprecated in JDK 9 in preparation for removal in a future release.-appclass app-class
Qualified name of the application class to be executed.
-classpath files
List of dependent JAR file names. In the heat of the night ost rar extractor.
-height height
Height of the application.
-name name
Name of the application.
-preloader preloader-class
Qualified name of the JavaFX preloader class to be executed. Use this option only for JavaFX applications. Don’t use for Java applications, including headless applications.
-v
Enables verbose output.
-width width
Width of the application.
Options for the signjar Command
Note:
The -signjar
command for the Java Packager tool is deprecated in JDK 9 in preparation for removal in a future release. It also doesn’t work with multirelease JAR files. Use the jarsigner tool to sign the JAR file.-alias key-alias
Alias for the key.
-keyPass password
Password for recovering the key.
-keyStore file
Keystore file name.
-outdir dir
Name of the directory that receives the generated output files.
-storePass password
Password to check the integrity of the keystore or unlock the keystore.
-storeType type
Keystore type. The default value is
jks
.-srcdir dir
Base directory of the files to pack.
-srcfiles files
List of files in
srcdir
. If omitted, all files in srcdir
(which is a mandatory argument in this case) will be packed.Arguments for Self-Contained Application Bundles
The
-Bbundler-argument=value
option for the -deploy
command is used when generating self-contained applications. This option enables you to set an argument for the bundler that’s used to create self-contained applications. To set more than one argument, pass an instance of this option for each argument. Each type of bundler has its own set of arguments.The following sections describe the valid arguments for the available bundlers:
General Bundler Arguments
![Convert .jar To .exe For Mac Convert .jar To .exe For Mac](https://i.ytimg.com/vi/sRgidIjl5tE/maxresdefault.jpg)
General bundler arguments are valid for all bundlers.
appVersion=version
Version of the application package. Some bundlers restrict the format of the version string.
arguments=option=value
Arguments to pass to the application when it is started. Enclose the argument list in quotes. To pass multiple options, separate the option-value pairs with spaces, for example:
classPath=path
Class path relative to the assembled application directory. The path is typically extracted from the JAR file manifest, and doesn’t need to be set if you’re using the other
javapackager
commands.dropinResourcesRoot=directory
Directory in which to look for bundler-specific drop-in resources. For example, on macOS, to look in the current directory for the
Info.plist
file, use the following:The file is then found in the current directory:
package/macosx/Info.plist
.icon=path
Location of the default icon to be used for application launchers and other assists.
Linux: The format must be
.png
.macOS: The format must be
.icns
.Windows: The format must be
.ico
.identifier=value
Default value that is used for other platform-specific values such as
mac.CFBundleIdentifier
. Reverse DNS order is recommended, for example, com.example.application.my-application
.jvmOptions=option
Option to be passed to the JVM when the application is run. Any option that is valid for the
java
command can be used. To pass more than one option, use multiple instances of the -B
option, as shown in the following example:jvmProperties=property=value
Java system property to be passed to the VM when the application is run. Any property that’s valid for the
-D
option of the java
command can be used. Specify both the property name and the value for the property. To pass more than one property, use multiple instances of the -B
option, as shown in the following example:mainJar=filename
Name of the JAR file that contains the main class for the application. The file name is typically extracted from the JAR file manifest, and doesn’t need to be set if you’re using the other
javapackager
commands.preferencesID=node
Preferences node to examine to check for JVM options that the user can override. The node specified is passed to the application at runtime as the option
-Dapp.preferences.id
. This argument is used with the userJVMOptions
argument.runtime=path
Location of the JRE or JDK to use with a Java Web Start application, valid only when the
-native
option is set to jnlp
.userJvmOptions=option=value
JVM options that users can override. Any option that’s valid for the
java
command can be used. Specify both the option name and the value for the option. To pass more than one option, use multiple instances of the -B
option, as shown in the following example:macOS Application Bundler Arguments
mac.category=category
Category for the application. The category must be in the list of categories found on the Apple Developer website.
mac.CFBundleIdentifier=value
Value stored in the info plist for
CFBundleIdentifier
. This value must be globally unique and contain only letters, numbers, dots, and dashes. Reverse DNS order is recommended, for example, com.example.application.my-application
.mac.CFBundleName=name
Name of the application as it appears on the macOS menu bar. A name of fewer than 16 characters is recommended. The default is the
name
attribute.mac.CFBundleVersion=value
Version number for the application, used internally. The value must be at least one integer and no more than three integers separated by periods (.) for example, 1.3 or 2.0.1. The value can be different than the value for the
appVersion
argument. If the appVersion
argument is specified with a valid value and the mac.CFBundleVersion
argument isn’t specified, then the appVersion
value is used. If neither argument is specified, then 100
is used as the version number.mac.signing-key-developer-id-app=key
Name of the signing key used for Developer ID or Gatekeeper signing. If you imported a standard key from the Apple Developer Website, then that key is used by default. If no key can be identified, then the application isn’t signed.
mac.bundle-id-signing-prefix=prefix
Prefix that is applied to the signed binary when binaries that lack plists or existing signatures are found inside the bundles.
macOS DMG (Disk Image) Bundler Arguments
The macOS DMG installer shows the license file specified by
licenseFile
, if provided, before allowing the disk image to be mounted.licenseFile=path
Location of the End User License Agreement (EULA) to be presented or recorded by the bundler. The path is relative to the packaged application resources, for example,
-BlicenseFile=COPYING
.systemWide=boolean
Flag that indicates which drag-to-install target to use. Set to
true
to show the Applications folder. Set to false
to show the Desktop folder. The default is true
.mac.CFBundleVersion=value
Version number for the application, used internally. The value must be at least one integer and no more than three integers separated by periods (.) for example, 1.3 or 2.0.1. The value can be different than the value for the
appVersion
argument. If the appVersion
argument is specified with a valid value and the mac.CFBundleVersion
argument isn’t specified, then the appVersion
value is used. If neither argument is specified, then 100
is used as the version number.mac.dmg.simple=boolean
Flag that indicates if DMG customization steps that depend on executing AppleScript code are skipped. Set to
true
to skip the steps. When set to true
, the disk window doesn’t have a background image, and the icons aren’t moved into place. If the systemWide
argument is also set to true
, then a symbolic link to the root Applications folder is added to the DMG file. If the systemWide
argument is set to false
, then only the application is added to the DMG file, no link to the desktop is added.macOS PKG Bundler Arguments
The macOS PKG installer presents a wizard and shows the license file specified by the
licenseFile
argument as one of the pages in the wizard. The user must accept the terms before installing the application.licenseFile=path
Location of the End User License Agreement (EULA) to be presented or recorded by the bundler. The path is relative to the packaged application resources, for example,
-BlicenseFile=COPYING
.mac.signing-key-developer-id-installer=key
Name of the signing key used for Developer ID or Gatekeeper signing. If you imported a standard key from the Apple Developer Website, then that key is used by default. If no key can be identified, then the application isn’t signed.
mac.CFBundleVersion=value
Version number for the application, used internally. The value must be at least one integer and no more than three integers separated by periods (.) for example, 1.3 or 2.0.1. The value can be different than the value for the
appVersion
argument. If the appVersion
argument is specified with a valid value and the mac.CFBundleVersion
argument isn’t specified, then the appVersion
value is used. If neither argument is specified, 100
is used as the version number.Mac App Store Bundler Arguments
mac.app-store-entitlements=path
Location of the file that contains the entitlements that the application operates under. The file must be in the format specified by Apple. The path to the file can be specified in absolute terms, or relative to the invocation of
javapackager
. If no entitlements are specified, then the application operates in a sandbox that’s stricter than the typical applet sandbox, and access to network sockets and all files is prevented.mac.signing-key-app=key
Name of the application signing key for the Mac App Store. If you imported a standard key from the Apple Developer Website, then that key is used by default. If no key can be identified, then the application isn’t signed.
mac.signing-key-pkg=key
Name of the installer signing key for the Mac App Store. If you imported a standard key from the Apple Developer Website, then that key is used by default. If no key can be identified, then the application isn’t signed.
mac.CFBundleVersion=value
Version number for the application, used internally. The value must be at least one integer and no more than three integers separated by periods (.) for example, 1.3 or 2.0.1. The value can be different than the value for the
appVersion
argument. If the appVersion
argument is specified with a valid value and the mac.CFBundleVersion
argument isn’t specified, then the appVersion
value is used. If neither argument is specified, then 100
is used as the version number. If this version is an upgrade for an existing application, then the value must be greater than previous version number.Linux Debian Bundler Arguments
The license file specified by the
licenseFile
argument isn’t presented to the user in all cases, but the file is included in the application metadata.category=category
Category for the application. See Registered Categories in Desktop Menu Specification for examples.
copyright=string
Copyright string for the application. This argument is used in the Debian metadata.
email=address
Email address used in the Debian Maintainer field.
licenseFile=path
Location of the End User License Agreement (EULA) to be presented or recorded by the bundler. The path is relative to the packaged application resources, for example,
-BlicenseFile=COPYING
.licenseType=type
Short name of the license type, such as
-BlicenseType=Proprietary
, or '-BlicenseType=GPL v2 + Classpath Exception'
.vendor=value
Corporation, organization, or individual providing the application. This argument is used in the Debian Maintainer field.
Linux RPM Bundler Arguments
category=category
Category for the application. See Registered Categories in Desktop Menu Specification for examples.
licenseFile=path
Location of the End User License Agreement (EULA) to be presented or recorded by the bundler. The path is relative to the packaged application resources, for example,
-BlicenseFile=COPYING
.licenseType=type
Short name of the license type, such as
-BlicenseType=Proprietary
, or '-BlicenseType=GPL v2 + Classpath Exception'
.vendor=value
Corporation, organization, or individual providing the application.
Windows EXE Bundler Arguments
copyright=string
Copyright string for the application. The string must be a single line no longer than 100 characters. This argument is used in various executable file and registry metadata.
installdirChooser=boolean
Flag that indicates if the user can choose the directory in which the application is installed. Set to
true
to show a dialog box for the user to choose the directory. Set to false
to install the application in the directory indicated by the systemWide
argument. The default is false
.licenseFile=path
Location of the End User License Agreement (EULA) to be presented or recorded by the bundler. The path is relative to the packaged application resources, for example,
-BlicenseFile=COPYING
.menuHint=boolean
Flag that indicates if a shortcut is installed on the Start menu or Start screen. Set to
true
to install the shortcut. The default is true
.shortcutHint=boolean
Flag that indicates if a shortcut is placed on the desktop. Set to
true
to add a shortcut to the desktop. The default is false
.systemWide=boolean
Flag that indicates if the application is installed in the
Program Files
directory or in the standard location in the users home directory. Set to true
to install the application in Program Files
. Set to false
to install the application in the user's home directory. The default is false
.win.menuGroup=group
Menu group in which to install the application when
menuHint
is true
. This argument is ignored when menuHint
is false
.vendor=value
Corporation, organization, or individual providing the application. This argument is used in various executable file and registry metadata.
Windows MSI Bundler Arguments
installdirChooser=boolean
Flag that indicates if the user can choose the directory in which the application is installed. Set to
true
to show a dialog box for the user to choose the directory. Set to false
to install the application in the directory indicated by the systemWide
argument. The default is false
.licenseFile=path
Location of the End User License Agreement (EULA) to be presented or recorded by the bundler. The path is relative to the packaged application resources, for example,
-BlicenseFile=COPYING
.menuHint=boolean
Flag that indicates if a shortcut is installed on the Start menu or Start screen. Set to
true
to install the shortcut. The default is true
.shortcutHint=boolean
Flag that indicates if a shortcut is placed on the desktop. Set to
true
to add a shortcut to the desktop. The default is false
.systemWide=boolean
Flag that indicates if the application is installed in the Program Files directory or in the standard location in the users home directory. Set to
true
to install the application in Program Files. Set to false
to install the application in the user's home directory. The default is true
.win.menuGroup=group
Menu group in which to install the application when
menuHint
is true
. This argument is ignored when menuHint
is false
.vendor=value
Corporation, organization, or individual providing the application. This argument is used in various executable file and registry metadata.
Deprecated Options
The following options are no longer used by the packaging tool and are ignored if present.
-embedCertificates
If present, the certificates will be embedded in the JNLP file. Deprecated
–deploy
option.-noembedlauncher
If present, the packager will not add the JavaFX launcher classes to the JAR file. Deprecated.
Notes
- A
-v
option can be used with any task command to enable verbose output. - When the
-srcdir
option is allowed in a command, it can be used more than once. If the-srcfiles
option is specified, then the files named in the argument are looked for in the location specified in the preceding-srcdir
option. If there is no-srcdir
preceding-srcfiles
, then the directory from which thejavapackager
command is executed is used.
Convert Mac Files To Windows
Examples
Packages the contents of the
classes
directory to outjar.jar
, and sets the application class to package.ClassName
.Generates
outfile.jnlp
and the corresponding outfile.html
files in outdir
for the application AppName
, which is started by package.ClassName
and has dimensions of 34 by 43 pixels.Note:
The -makeall
command for the Java Packager tool is deprecated in JDK 9 in preparation for removal in a future release.Does all the packaging work including compilation,
createjar
, and deploy
.Note:
Convert .jar To .exe For Mac Pro
The-signjar
command for the Java Packager tool is deprecated in JDK 9 in preparation for removal in a future release. It also doesn’t work with multirelease JAR files. Use the jarsigner tool to sign the JAR file.Signs all of the JAR files in the
dist
directory, attaches a certificate with the specified alias, keyStore
and storePass
, and puts the signed JAR files back into the dist
directory.Linux:
Generates the native Linux Debian package for running the
BrickBreaker
application as a self-contained application.Windows:
Convert .jar To .exe For Mac Free
Generates the native Windows EXE package for running the
BrickBreaker
application as a self-contained application.