Eclipse导出Java可运行JAR后无输出（图片不显示）及调试方法咨询

Hey there! Let's work through debugging your runnable JAR issue—this is a super common problem when moving from Eclipse to a standalone JAR, so I’ve got a few tried-and-true methods to help you track down what’s going wrong:

Double-clicking a JAR often hides error messages that would tell you exactly what’s broken. Instead, open a terminal or command prompt, navigate to your JAR’s directory, and run:
java -jar YourProjectName.jar
This will print any exceptions (like missing dependencies, invalid file paths, or class not found errors) right to the console. 9 times out of 10, this reveals the root cause immediately—whether it’s a missing dependency JAR or a broken path for your result images.

Since your project relies on local JARs, Eclipse’s export settings might not have included them correctly. When you exported the runnable JAR, you had three options for handling dependencies—let’s check which you used:

• Extract required libraries into generated JAR: Unzip your JAR and make sure all classes from your local dependencies are present. If some are missing, re-export and confirm this option is selected.
• Package required libraries into generated JAR: This bundles dependencies inside your JAR but uses a custom class loader. Sometimes this causes conflicts—try switching to the "copy to sub-folder" option instead if this is what you picked.
• Copy required libraries into a sub-folder next to the generated JAR: This is the most reliable choice. Ensure the lib sub-folder (or whatever name you chose) is in the same directory as your JAR, and that all your local JARs are inside it. If the folder is missing or incomplete, that’s your issue.

Paths that work in Eclipse often break in a JAR because the file structure changes. If you’re using File objects to load images (like new File("G:/project/images/result.png")), this looks for an absolute path that won’t exist on other machines (or even your own if you move the JAR).
Instead, load images as resources from inside the JAR using the class loader:

// Make sure your images are in the source folder (e.g., src/images) so they get packaged into the JAR
InputStream imageStream = getClass().getResourceAsStream("/images/result.png");
if (imageStream == null) {
    System.err.println("Could not find result.png in JAR resources!");
    return;
}
Image resultImage = ImageIO.read(imageStream);

This method works regardless of where the JAR is placed, as long as the images are packaged correctly.

If you need to debug line-by-line like you do in Eclipse, enable remote debugging:

1. Run your JAR with this command:
   java -jar -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005 YourProjectName.jar
   The suspend=y flag will pause the JAR until you connect with Eclipse.
2. In Eclipse, go to Run > Debug Configurations > Remote Java Application.
3. Create a new configuration, set Host to localhost and Port to 5005, then click Debug.
   Now you can set breakpoints and debug the JAR exactly like you would in your Eclipse project.

Unzip your JAR and look at META-INF/MANIFEST.MF to confirm:

• The Main-Class entry points to your correct main class (e.g., com.yourproject.Main).
• If you’re using external JARs, the Class-Path entry lists them correctly. For example, if dependencies are in a lib folder, it should look like:
  Class-Path: lib/dependency1.jar lib/dependency2.jar

Start with the command line run first—it’s the quickest way to get actionable error info. Let me know if you find a specific error and need help troubleshooting further!

内容的提问来源于stack exchange，提问作者beta