How to Make a JAR File in Eclipse | Java JAR

To make a JAR file in Eclipse for a small Java project, sending loose source folders is rarely the friendliest move. A JAR file (Java ARchive) packages compiled classes and related resources into one ZIP-based file. Eclipse can create it with its Export wizard, but exporting and running are two separate jobs. This guide keeps the original click-by-click route while making that distinction clear.

What a Java JAR File Contains

A JAR can contain compiled .class files, resources such as properties files, and a manifest. It is useful for sharing a library or a small application. A normal JAR is not automatically executable just because it exists: for java -jar to work, its manifest needs a Main-Class entry that points to a class with public static void main(String[] args).

Before You Export a JAR File in Eclipse

First, make sure the project builds without errors and that you can run its intended main class from Eclipse. The export wizard packages what is selected; it does not fix compiler errors or guess which entry point you meant. If your project uses libraries, decide whether the recipient will provide those dependencies separately or whether you need a runnable package that includes them. For modern dependency-managed applications, Maven or Gradle may be a better distribution route, but Eclipse's built-in export remains useful for a small plain-Java project.

How to Make a JAR File in Eclipse

Step 1: In Package Explorer, select the project or the resources you intend to export. Be ready with a working project first; a JAR is a package for the work you have already compiled.

Step 2: Choose File > Export. The Export wizard opens. Expand Java, select JAR file, then select Next.

Step 3: Tick the resources you want in the JAR. Avoid exporting accidental workspace material such as a second project or local notes. Use Browse to choose a destination and file name, for example my-project.jar.

Step 4: On the JAR Packaging page, keep the defaults unless you know why a setting needs changing. The important part is that the selected compiled output and any required resources are included. Select Next.

Step 5: Eclipse then shows JAR Manifest Specification. For a library JAR, the defaults may be enough. For an application you expect to launch with java -jar, select the class that contains your main method as the Main class. Finish the wizard. Eclipse writes the JAR to the location you chose.

Check the Exported JAR

Find the file in Finder or File Explorer. A coffee-cup icon is only an operating-system association; it does not prove the archive has the right entry point. The most reliable check is a terminal in the JAR's directory:

jar tf my-project.jar
java -jar my-project.jar

jar tf lists the archive contents. If java -jar reports that no main manifest attribute exists, return to the Eclipse manifest step and select the intended Main class. If it reports a missing class, the JAR may need a dependency on the classpath or a different packaging method. Do not rename a ZIP file to .jar and expect Java to make it runnable.

Importing an Existing JAR into Eclipse

Importing a JAR is not the opposite of exporting a Java project. File > Import > General > Archive File can unpack an archive into your workspace, but an imported compiled JAR is not automatically editable source code. If you need to use another project's JAR, add it to that project's build path; if you need to edit its source, obtain the source project or source attachment instead.

For the old click-through exercise, choose File > Import, select General > Archive File, browse to the archive and inspect what Eclipse will copy. Finish only after choosing an appropriate destination. A project archive and a distributable application JAR are different things, even though both can travel as files.

One Final JAR Check

A JAR file is simply a sensible container, not a magic deployment button. Keep the project buildable, give the archive a clear name and test it from outside Eclipse before sending it on. For the current Java tools themselves, use the official Java documentation; for another small Java exercise, continue with our first Java demo program. Export conquered, dude.