Java deployment

suggest change


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.


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:

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.

Feedback about page:

Optional: your email if you want me to get back to you:

Table Of Contents