Bear Bibeault wrote:Hmm, doesn't sound like a good long-term strategy. Is this an application solely for your own use? If not, you will have no control over which version your customers/clients are using.
I'd spend my time finding out what the problem was.
I'm not doing this as a long term strategy. I'd like to be able to have the application RUN in the short term.
THEN I can figure out what is going on. The problem is, there is no error reported of ANY kind, so in the short term it isn't a simple thing to fix.
PLEASE help me to simply install 1.6.0 update 18 JDK. This is something that SHOULD be utter CAKE to do...
Bear Bibeault wrote:That said, are you sure that 18 isn't still there? If it is, there may be a way to make it the "official" version.
Take a peek in /System/Library/Frameworks/JavaVM.framework/Versions
I don't think Apple ever let you have two versions of the same JDK level (like Java 6) simultaneously. Used to be you could have the latest Java 1.3, latest Java 1.4, latest Java 5 etc. all in parallel, but not two different builds of, say, Java 6.
Have you tried running the application in debug mode in Eclipse, with a breakpoint right at the beginning in main(), so that you can step through it? Maybe you'll discover that way where exactly it crashes.