代码在IDE中可正常运行，打包为.jar文件后却无法运行

Hey there! It’s super common for apps that work great in the IDE to break when packaged into a JAR—let’s walk through the most likely culprits and fixes for your case:

1. Tess4J’s Native Library Files Are Missing #

Tess4J relies on native libraries (like libtesseract.dll on Windows, libtesseract.so on Linux, or libtesseract.dylib on macOS) to handle OCR tasks. Your IDE probably picks these up automatically from your dependencies, but they don’t get bundled into the JAR by default.

Fixes:

• Drop the required native library files into the same folder as your JAR. When you run the JAR, Java will check this location for native libraries.
• If you use Maven/Gradle, use plugins like Maven Shade or Gradle Shadow to bundle native libraries into the JAR, then add code to extract and load them at runtime (e.g., System.loadLibrary("tesseract") after setting the correct library path).

2. Missing Dependencies in the JAR #

Your IDE manages all project dependencies (like Tess4J’s own JAR files) behind the scenes, but a basic JAR export won’t include these. Without them, Java can’t find the classes needed to run your app.

Fixes:

• Build a "fat JAR"—a single JAR that includes your app code plus all dependencies. Most IDEs have built-in options for this, or use the build tool plugins mentioned above.
• For manual setup, place all dependency JARs in the same folder as your app’s JAR, then run it with:

  java -cp "your-app.jar;*.jar" com.yourpackage.YourMainClassName
  

  (Use : instead of ; as the path separator on Linux/macOS.)

3. Incorrect Resource/File Paths #

While your JFileChooser pointing to C: might not be the issue, Tess4J needs access to its tessdata folder (with OCR language packs) to function. If this folder isn’t accessible when running the JAR, it’ll fail silently or throw errors.

Fixes:

• Keep the tessdata folder in the same directory as your JAR, then explicitly set its path in code:

  ITesseract tesseract = new Tesseract();
  tesseract.setDatapath("tessdata"); // Points to the folder next to the JAR
  

• Avoid hardcoded absolute paths—use Class.getResource() or Class.getResourceAsStream() to load resources if you bundle them into the JAR.

4. Missing or Incorrect Main Class in JAR Manifest #

If your JAR doesn’t know which class contains the main() method, it won’t know where to start running your app.

Fixes:

• When exporting from your IDE, make sure you select the correct class with the main() method as the "Main Class" in the export settings.
• Check the MANIFEST.MF file inside your JAR (open it with a text editor) to ensure it has a line like:

  Main-Class: com.yourpackage.YourMainClassName
  

  (Note the space after the colon, and ensure there’s a blank line at the end of the file.)

5. Swing UI Thread Violations #

While your IDE might let you get away with creating Swing components outside the Event Dispatch Thread (EDT), standalone JARs can behave unpredictably here. Swing requires all UI code to run on the EDT.

Fix:
Wrap your entire GUI setup code inside SwingUtilities.invokeLater() to ensure it runs on the correct thread:

public static void main(String[] args) {
    SwingUtilities.invokeLater(() -> {
        // Your full GUI code goes here
        JButton open = new JButton();
        JFileChooser fc = new JFileChooser();
        fc.setCurrentDirectory(new java.io.File("C:"));
        fc.setDialogTitle("Classificador de Documentos");
        if (fc.showOpenDialog(open) == JFileChooser.APPROVE_OPTION) {
            // Handle selected file
        }
        JFrame wait = new JFrame("Resultado");
        wait.setVisible(true);
        wait.setSize(300, 300);
        JLabel labelwait = new JLabel("Loading");
        JPanel panelwait = new JPanel();
        panelwait.add(labelwait);
        wait.add(panelwait);
        wait.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
    });
}

Pro Debugging Tip #

Always run your JAR from the command line using java -jar your-app.jar—this will show you error messages (like ClassNotFoundException or UnsatisfiedLinkError) that are hidden when double-clicking the JAR. These messages will tell you exactly what’s missing or broken.

内容的提问来源于stack exchange，提问作者Mário Ribeiro