I’ll keep this short: jar manifests suck. I just found out a jar wasn’t loaded as it was supposed to because my manifest classpath entry was 70 chars long (including the first space!). All other lines were 71 chars long, except this one because the entry was finished, so I was missing one space.
Netbeans handles this nicely when I build my app consisting of a number of projects with jar dependencies. Everything ends up ready to run in the dist dir of the main project root. Neat and simple. In Eclipse I seem to overlook the ability to export a Jar with it’s dependencies’ classpath preconfigured & packaged alongside the project code. I mean, am I *supposed* to do this myself?
I guess I really need to upgrade to using ant or maven and automate these kinds of things … and I will! Euhm … soon!
Since this is a clientside project, I’ll finally make the step and get the right kind of certificate to sign my code and WebStart enable the entire thing. And unless I solve these issues, I’ll return to netbeans for that purpose, although MyEclipse finally enabled me to stick with Eclipse 
Until I switch to something automated of course 
Tired now. Need sleep.
Nite nite.
PS: I was about to reread but I’m too tired, so sorry, it’s probably badly written and ill-structured (or something)