Java Tutorial2D Graphics in JavaJava Stack-Walking APIClass - Java ReflectionCommon Java PitfallsDocumenting Java CodeGenerating Java CodeInstalling Java (Standard Edition)Java AgentsJava Alternative CollectionsJava AnnotationsJava Apache Commons LangJava AppDynamics and TIBCO BusinessWorks Instrumentation for Easy IntegrationJava AppletsJava ArraysJava AssertingJava Atomic TypesJava AudioJava AutoboxingJava Basic Control StructuresJava BenchmarksJava BigDecimalJava BigIntegerJava Bit ManipulationJava BufferedWriterJava ByteBufferJava Bytecode ModificationJava C++ ComparisonJava Calendar and its SubclassesJava Character encodingJava Choosing CollectionsJava Classes and ObjectsJava ClassloadersJava Collection Factory MethodsJava CollectionsJava Command line Argument ProcessingJava Comparable and ComparatorJava Compiler - javacJava CompletableFutureJava Concurrent CollectionsJava Concurrent Programming (Threads)Java Console I/OJava ConstructorsJava Converting to and from StringsJava Creating Images ProgrammaticallyJava Currency and MoneyJava Date ClassJava Dates and Time (java.time.*)Java Default MethodsJava deploymentJava Dequeue InterfaceJava Disassembling and DecompilingJava Dynamic Method DispatchJava Editions, Versions, Releases and DistributionsJava EncapsulationJava Enum MapJava Enum starting with numberJava EnumsJava EnumSet classJava Exceptions and exception handlingJava Executor, ExecutorService and Thread poolsJava ExpressionsJava File I/OJava FileUpload to AWSJava Floating Point OperationsJava Fluent InterfaceJava FTP (File Transfer Protocol)Java Functional InterfacesJava GenericsJava Getters and SettersJava HashtableJava HttpURLConnectionJava Immutable ClassJava Immutable ObjectsJava InheritanceJava InputStreams and OutputStreamsJava InterfacesJava Iterator and IterableJava JavaBeanJava JAX-WSJava JAXBJava JMXJava JNDIJava JShellJava Just in Time (JIT) compilerJava JVM FlagsJava JVM Tool InterfaceJava Lambda ExpressionsJava LinkedHashMapJava List vs SET

Java deployment

From WikiOD

There are a variety of technologies for "packaging" Java applications, webapps and so forth, for deployment to the platform on which they will run. They range from simple library or executable JAR files, WAR and EAR files, through to installers and self-contained executables.

Remarks[edit | edit source]

At the most fundamental level, a Java program can be deployed by copying a compiled class (i.e. a ".class" file) or a directory tree containing compiled classes. However Java is normally deployed in one of the following ways:

  • By copying a JAR file or collection of JAR files to the system where they will be executed; e.g. using javac.
  • By copying or uploading a WAR, EAR or similar file to a "servlet container" or "application server".
  • By running some kind of application installer that automates the above. The installer might also install an embedded JRE.
  • By putting the JAR files for the application onto a web server to allow them to be launched using Java WebStart.

The Creating JAR, WAR and EAR files example summarizes the different ways to create these files.

There are numerous open source and commercial "installer generator" and "EXE generator" tools for Java. Similarly, there are tools for obfuscating Java class files (to make reverse engineering harder) and for adding runtime license checking. These are all out of scope for the "Java Programming Language" documentation.

Making an executable JAR from the command line[edit | edit source]

To make a jar, you need one or more class files. This should have a main method if it is to be run by a double click.

For this example, we will use:

import javax.swing.*;
import java.awt.Container;

public class HelloWorld {

    public static void main(String[] args) {
        JFrame f = new JFrame("Hello, World"); 
        JLabel label = new JLabel("Hello, World");
        Container cont = f.getContentPane();


It has been named

Next, we want to compile this program.

You may use any program you want to do this. To run from the command line, see the documentation on compiling and running your first java program.

Once you have HelloWorld.class, make a new folder and call it whatever you want.

Make another file called manifest.txt and paste into it

Main*Class: HelloWorld
Class*Path: HelloWorld.jar

Put it in the same folder with HelloWorld.class

Use the command line to make your current directory (cd C:\Your\Folder\Path\Here on windows) your folder.

Use Terminal and change directory to the directory (cd /Users/user/Documents/Java/jarfolder on Mac) your folder

When that is done, type in jar -cvfm HelloWorld.jar manifest.txt HelloWorld.class and press enter. This makes a jar file (in the folder with your manifest and HelloWorld.class) using the .class files specified and named HelloWorld.jar. See the Syntax section for information about the options (like -m and -v).

After these steps, go to your directory with the manifest file and you should find HelloWorld.jar

Clicking on it should display Hello, World in a text box.

Creating JAR, WAR and EAR files[edit | edit source]

The JAR, WAR and EAR files types are fundamentally ZIP files with a "manifest" file and (for WAR and EAR files) a particular internal directory / file structure.

The recommended way to create these files is to use a Java-specific build tool which "understands" the requirements for the respective file types. If you don't use a build tool, then IDE "export" is the next option to try.

(Editorial note: the descriptions of how to create these files are best placed in the documentation for the respective tools. Put them there. Please show some self-restraint and DON'T shoe-horn them into this example!)

Creating JAR and WAR files using Maven[edit | edit source]

Creating a JAR or WAR using Maven is simply a matter of putting the correct <packaging> element into the POM file; e,g,




For more details. Maven can be configured to create "executable" JAR files by adding the requisite information about the entry-point class and external dependencies as plugin properties for the maven jar plugin. There is even a plugin for creating "uberJAR" files that combine an application and its dependencies into a single JAR file.

Please refer to the Maven documentation ( )for more information.

Creating JAR, WAR and EAR files using Ant[edit | edit source]

The Ant build tool has separate "tasks" for building JAR, WAR and EAR. Please refer to the Ant documentation ( ) for more information.

Creating JAR, WAR and EAR files using an IDE[edit | edit source]

The three most popular Java IDEs all have built-in support for creating deployment files. The functionality is often described as "exporting".

Creating JAR, WAR and EAR files using the jar command.[edit | edit source]

It is also possible to create these files "by hand" using the jar command. It is simply a matter of assembling a file tree with the correct component files in the correct place, creating a manifest file, and running jar to create the JAR file.

Please refer to the jar command Topic ( Creating and modifying JAR files ) for more information

Introduction to Java Web Start[edit | edit source]

The Oracle Java Tutorials summarize Web Start as follows:

Java Web Start software provides the power to launch full-featured applications with a single click. Users can download and launch applications, such as a complete spreadsheet program or an Internet chat client, without going through lengthy installation procedures.

Other advantages of Java Web Start are support for signed code and explicit declaration of platform dependencies, and support for code caching and deployment of application updates.

Java Web Start is also referred to as JavaWS and JAWS. The primary sources of information are:

Prerequisites[edit | edit source]

At a high level, Web Start works by distributing Java applications packed as JAR files from a remote webserver. The prerequisites are:

  • A pre-existing Java installation (JRE or JDK) on the target machine where the application is to run. Java 1.2.2 or higher is required:
    • From Java 5.0 onwards, Web Start support is included in the JRE / JDK.
    • For earlier releases, Web Start support is installed separately.
    • The Web Start infrastructure includes some Javascript that can be included in a web page to assist the user to install the necessary software.
  • The webserver that hosts the software must be accessible to the target machine.
  • If the user is going to launch a Web Start application using a link in a web page, then:
    • they need a compatible web browser, and
    • for modern (secure) browsers, they need to be told how to tell the browser to allow Java to run ... without compromising web browser security.

An example JNLP file[edit | edit source]

The following example is intended to illustrate the basic functionality of JNLP.

<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="" 
        <vendor>The Team</vendor>
        <!-- Application Resources -->
        <j2se version="1.7+" href=""/>
        <jar href="Demo.jar" main="true"/>
         name="Demo Application"
     <update check="background"/>

As you can see, a JNLP file XML-based, and the information is all contained in the <jnlp> element.

  • The spec attribute gives the version of the JNPL spec that this file conforms to.
  • The codebase attribute gives the base URL for resolving relative href URLs in the rest of the file.
  • The href attribute gives the definitive URL for this JNLP file.
  • The <information> element contains metadata the application including its title, authors, description and help website.
  • The <resources> element describes the dependencies for the application including the required Java version, OS platform and JAR files.
  • The <application-desc> (or <applet-desc>) element provides information needed to launch the application.

Setting up the web server[edit | edit source]

The webserver must be configured to use application/x-java-jnlp-file as the MIMEtype for .jnlp files.

The JNLP file and the application's JAR files must be installed on the webserver so that they are available using the URLs indicated by the JNLP file.

Enabling launch via a web page[edit | edit source]

If the application is to be launched via a web link, the page that contains the link must be created on the webserver.

If you can assume that Java Web Start is already installed on the user's machine, then the web page simply needs to contain a link for launching the application. For example.

<a href="">Launch the application</a>

Otherwise, the page should also include some scripting to detect the kind of browser the user is using and request to download and install the required version of Java.

NOTE: It is a bad idea to encourage users to encourage to install Java this way, or even to enable Java in their web browsers so that JNLP web page launch will work.

Launching Web Start applications from the command line[edit | edit source]

The instructions for launching an Web Start application from the command line are simple. Assuming that the user has a Java 5.0 JRE or JDK installed, the simply need to run this:

$ javaws <url>

where <url> is the URL for the JNLP file on the remote server.

Creating an UberJAR for an application and its dependencies[edit | edit source]

A common requirement for a Java application is that can be deployed by copying a single file. For simple applications that depend only on the standard Java SE class libraries, this requirement is satisfied by creating a JAR file containing all of the (compiled) application classes.

Things are not so straightforward if the application depends on third-party libraries. If you simply put dependency JAR files inside an application JAR, the standard Java class loader will not be able to find the library classes, and your application will not start. Instead, you need to create a single JAR file that contains the application classes and associated resources together with the dependency classes and resources. These need to be organized as a single namespace for the classloader to search.

The such a JAR file is often referred to as an UberJAR.

Creating an UberJAR using the "jar" command[edit | edit source]

The procedure for creating an UberJAR is straight-forward. (I will use Linux commands for simplicity. The commands should be identical for Mac OS, and similar for Windows.)

Create a temporary directory, and change directory to it.

$ mkdir tempDir
$ cd tempDir

For each dependent JAR file, in the reverse order that they need to appear on the application's classpath, used the jar command to unpack the JAR into the temporary directory.

$ jar -xf <path/to/file.jar>

Doing this for multiple JAR files will overlay contents of the JARs.

Copy the application classes from the build tree into the temporary directory

$ cp -r path/to/classes .

Create the UberJAR from the contents of the temporary directory:

$ jar -cf ../myApplication.jar

If you are creating an executable JAR file, include an appropriate MANIFEST.MF as described here.

Creating an UberJAR using Maven[edit | edit source]

If your project is built using Maven, you can get it to create an UberJAR using either the "maven-assembly" or "maven-shade" plugins. See the Maven Assembly topic (in the Maven documentation) for details.

The advantages and drawbacks of UberJARs[edit | edit source]

Some of advantages of UberJARs are self-evident:

  • An UberJAR is easy to distribute.
  • You cannot break the library dependencies for an UberJAR, since the libraries are self-contained.

In addition, if you use an appropriate tooling to create the UberJAR, you will have the option of excluding library classes that are not used from the JAR file. However, that this is typically done by static analysis of the classes. If your application uses reflection, annotation processing and similar techniques, you need to be careful that classes are not excluded incorrectly.

UberJARs also have some disadvantages:

  • If you have lots of UberJARs with the same dependencies, then each one will contain a copy of the dependencies.
  • Some open source libraries have licenses which may preclude 1 their use in an UberJAR.

1 - Some open source library licenses allow you to use the library only of the end-user is able to replace one version of the library with another. UberJARs can make replacement of version dependencies difficult.