Yeah, I'm at home, and I've confirmed that the .class files that Eclipse exports in its jar are the only reason the jar doesn't run.
ie. If i copy over NetBeans' .class files from its jar into my Eclipse jar, the program runs just fine on my Instinct.
It could be anything - a compiler bug or who knows what else. When you say the class files are the only reason it doesn't run, that almost like saying "the exe I compiled with Visual Studio runs, but the exe I compiled with GCC doesn't". They are two completely different environments with completely different outputs.
I stuck with Netbeans since it's clear that most mobile development, particularly from Sprint, is based on Netbeans. But then again, you are from Vancouver; isn't there a big IBM site in Vancouver?
A few things you could try
- reducing the obfuscation level, because I have heard of obfuscator issues
- decompiling the class files and comparing