This guide details the process of creating a JAR file from a Java source file. We'll cover each step with explanations and examples.
Step 1: Java Code Creation
Create a .java
file containing your Java code. For instance, a file named Main.java
might look like this:
public class Main { public static void main(String[] args) { System.out.println("Hello, World!"); } }
This is your source code, adhering to Java's syntax and rules.
Step 2: Compilation
Compile the .java
file using the Java compiler (javac
):
javac Main.java
This generates a .class
file (e.g., Main.class
) containing bytecode – machine-readable instructions for the Java Virtual Machine (JVM). Each .java
file produces a corresponding .class
file.
Step 3: Manifest File (Optional)
Create a MANIFEST.MF
file (optional but recommended) to define JAR metadata. For example:
<code>Main-Class: Main</code>
Main-Class
specifies the application's entry point (the class with the main
method). This simplifies JAR execution.
Step 4: JAR File Packaging
Use the jar
command to package the .class
file(s), resources, and (optionally) the manifest file into a JAR:
jar cvfm MyApplication.jar MANIFEST.MF Main.class
c
: Creates a new JAR.v
: Enables verbose output (shows the packaging process).f
: Specifies the output JAR filename (MyApplication.jar
).m
: Includes the manifest file (MANIFEST.MF
).
The jar
tool creates a single, portable archive (MyApplication.jar
) containing all compiled components.
Step 5: JAR File Testing
Run the JAR file to verify its functionality:
java -jar MyApplication.jar
Successful execution should produce the output:
<code>Hello, World!</code>
The JVM uses the MANIFEST.MF
(if present) to locate the Main-Class
and execute its main
method.
Step 6: JAR File Deployment
Deployment depends on the target environment:
- Standalone: Copy the JAR to the target machine and run it using
java -jar
. - Microservices (e.g., Spring Boot): Deploy the "fat JAR" (containing an embedded server) using
java -jar
. - Containerized (Docker): Use a Dockerfile:
FROM openjdk:17 COPY MyApplication.jar /app/MyApplication.jar WORKDIR /app CMD ["java", "-jar", "MyApplication.jar"]
Build (docker build -t my-java-app .
) and run (docker run -p 8080:8080 my-java-app
) the container.
- Cloud: Deploy to cloud platforms (AWS, GCP, Azure) via CI/CD or cloud-specific services.
Execution Summary:
- Write Java code (
.java
). - Compile to
.class
files usingjavac
. - (Optional) Create
MANIFEST.MF
. - Package into a JAR using
jar
. - Test the JAR using
java -jar
. - Deploy to the appropriate environment.
The above is the detailed content of Journey From Java file to a JAR file. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Enums in Java are special classes that represent fixed number of constant values. 1. Use the enum keyword definition; 2. Each enum value is a public static final instance of the enum type; 3. It can include fields, constructors and methods to add behavior to each constant; 4. It can be used in switch statements, supports direct comparison, and provides built-in methods such as name(), ordinal(), values() and valueOf(); 5. Enumeration can improve the type safety, readability and flexibility of the code, and is suitable for limited collection scenarios such as status codes, colors or week.

Interface Isolation Principle (ISP) requires that clients not rely on unused interfaces. The core is to replace large and complete interfaces with multiple small and refined interfaces. Violations of this principle include: an unimplemented exception was thrown when the class implements an interface, a large number of invalid methods are implemented, and irrelevant functions are forcibly classified into the same interface. Application methods include: dividing interfaces according to common methods, using split interfaces according to clients, and using combinations instead of multi-interface implementations if necessary. For example, split the Machine interfaces containing printing, scanning, and fax methods into Printer, Scanner, and FaxMachine. Rules can be relaxed appropriately when using all methods on small projects or all clients.

Java supports asynchronous programming including the use of CompletableFuture, responsive streams (such as ProjectReactor), and virtual threads in Java19. 1.CompletableFuture improves code readability and maintenance through chain calls, and supports task orchestration and exception handling; 2. ProjectReactor provides Mono and Flux types to implement responsive programming, with backpressure mechanism and rich operators; 3. Virtual threads reduce concurrency costs, are suitable for I/O-intensive tasks, and are lighter and easier to expand than traditional platform threads. Each method has applicable scenarios, and appropriate tools should be selected according to your needs and mixed models should be avoided to maintain simplicity

There are three main differences between Callable and Runnable in Java. First, the callable method can return the result, suitable for tasks that need to return values, such as Callable; while the run() method of Runnable has no return value, suitable for tasks that do not need to return, such as logging. Second, Callable allows to throw checked exceptions to facilitate error transmission; while Runnable must handle exceptions internally. Third, Runnable can be directly passed to Thread or ExecutorService, while Callable can only be submitted to ExecutorService and returns the Future object to

In Java, enums are suitable for representing fixed constant sets. Best practices include: 1. Use enum to represent fixed state or options to improve type safety and readability; 2. Add properties and methods to enums to enhance flexibility, such as defining fields, constructors, helper methods, etc.; 3. Use EnumMap and EnumSet to improve performance and type safety because they are more efficient based on arrays; 4. Avoid abuse of enums, such as dynamic values, frequent changes or complex logic scenarios, which should be replaced by other methods. Correct use of enum can improve code quality and reduce errors, but you need to pay attention to its applicable boundaries.

JavaNIO is a new IOAPI introduced by Java 1.4. 1) is aimed at buffers and channels, 2) contains Buffer, Channel and Selector core components, 3) supports non-blocking mode, and 4) handles concurrent connections more efficiently than traditional IO. Its advantages are reflected in: 1) Non-blocking IO reduces thread overhead, 2) Buffer improves data transmission efficiency, 3) Selector realizes multiplexing, and 4) Memory mapping speeds up file reading and writing. Note when using: 1) The flip/clear operation of the Buffer is easy to be confused, 2) Incomplete data needs to be processed manually without blocking, 3) Selector registration must be canceled in time, 4) NIO is not suitable for all scenarios.

Javaprovidesmultiplesynchronizationtoolsforthreadsafety.1.synchronizedblocksensuremutualexclusionbylockingmethodsorspecificcodesections.2.ReentrantLockoffersadvancedcontrol,includingtryLockandfairnesspolicies.3.Conditionvariablesallowthreadstowaitfor

Java's class loading mechanism is implemented through ClassLoader, and its core workflow is divided into three stages: loading, linking and initialization. During the loading phase, ClassLoader dynamically reads the bytecode of the class and creates Class objects; links include verifying the correctness of the class, allocating memory to static variables, and parsing symbol references; initialization performs static code blocks and static variable assignments. Class loading adopts the parent delegation model, and prioritizes the parent class loader to find classes, and try Bootstrap, Extension, and ApplicationClassLoader in turn to ensure that the core class library is safe and avoids duplicate loading. Developers can customize ClassLoader, such as URLClassL
