Member Avatar for dtpp

Ive been having this issue for quite a long time. When coding in Java my IDE (Eclipse) will not allow me to create JAR file.

Ive googled quite alot only to see there is no direct solution to this and the causing factor may be Win8.1. I thought - ok no problem. Got myself a VirtualBox, scrapped Manjaro (Arch derrativate) and installed Eclipse from pacman (brand new edition), imported project. It runs ok, when I try to create JAR, it crashes. Logfile (var/log/eclipse/jarfile.log) is empty.

Any suggestions?

Edited by dtpp
  • 4 Contributors
  • 6 Replies
  • 247 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by stultuske

Dani AI

Generated

A focused troubleshooting checklist for an Eclipse crash that happens only during JAR export and leaves no obvious console output — built from the thread (notes from and the earlier requests by , and ). The steps isolate whether the problem is a native/SWT crash, a JVM/Eclipse bitness or packaging mismatch, a workspace/plugin issue, or something project-specific.

Run Eclipse from a terminal and capture all output (Linux example shown; Windows can use the same redirection from a cmd prompt):

/path/to/eclipse/eclipse -clean -consoleLog > ~/eclipse-export.log 2>&1

Check the workspace log for plugin or Java exceptions:

tail -n 200 <workspace>/.metadata/.log
grep -i -E "error|exception|stacktrace|segfault" <workspace>/.metadata/.log

Search the filesystem for JVM crash dumps (native crashes produce hs_err_pid*.log):

find ~ -maxdepth 4 -name "hs_err_pid*.log"

Try creating the JAR outside Eclipse to see if the JDK toolchain itself works:

cd <project>/bin
jar cf ../myapp.jar .

Verify Eclipse and Java architectures match (32-bit vs 64-bit):

java -version
file /path/to/eclipse/eclipse

If those checks point to a native/SWT issue, try forcing GTK2 or switching the SWT backend before blaming the project:

export SWT_GTK3=0
/path/to/eclipse/eclipse -clean -consoleLog

Or add to eclipse.ini:

--launcher.GTK_version
2

Also try launching Eclipse with an explicit JDK via -vm (point to a different JVM, e.g., Oracle vs OpenJDK), or use the official Eclipse download instead of the distro package (pacman builds sometimes differ). Create a fresh workspace and a tiny HelloWorld project — if export works there, the problem is workspace/plugin or project config.

What to look for: native crash dumps (hs_err_pid) indicate JVM/SWT/native issues; .metadata/.log entries show plugin or workspace exceptions; a successful manual jar rules out the JDK toolchain. Follow this sequence (capture the terminal log first) to narrow the cause before changing Eclipse/JVM installs.

Recommended Answers

All 6 Replies

Member Avatar for JamesCherrill

What do you mean "will not allow me"? Is there an error message? What does your jar spec look like?

Member Avatar for Szabi Zsoldos

This is weird, could you show us the console please?

Member Avatar for dtpp

console shows nothing.

Member Avatar for JamesCherrill

Exactly which version of Eclipse have you installed, and exactly which version of Java?

Member Avatar for dtpp

Eclipse from June - Mars :)
Java 8

Member Avatar for stultuske

how do you see eclipse crashes while creating a jar if you don't get an error in your console?
is there any indication there's something wrong?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.