Barking Up the Wrong Tree.

1247739501000 » Tagged as: netbeans , RIA

Thought of trying out Aptana for two reasons; the first being the fact that it has support for Adobe Air and secondly I wanted try to an alternative to Netbeans cause Netbeans 6.7 is such a memory hog. Netbeans has always been a memory hog but this version really takes the cake. It's is worse than previous versions. The release candidate were absolute nightmares I was worried that my drives would be swapped to death. As for Aptana, it cannot be installed with YUM. You have to download the zip and install it manually and such installations usually lead to errors.

(AptanaStudio:12284): Gtk-WARNING **: Unable to locate theme engine in module_path: "nodoka",

(AptanaStudio:12284): Gtk-WARNING **: Unable to locate theme engine in module_path: "nodoka", (Build 1.5.0.25497) [ERROR] Unable to determine current running state of Aptana Studio org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)] at org.eclipse.swt.SWT.error(SWT.java:3910) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:483) This is on Fedora 11 (64 bit). Then I tried a different machine (also Fedora 11 64bit, but one which had every possible package under the sun installed on it). There I get a different error.

(Build 1.5.0.25497) [ERROR] Unable to determine current running state of Aptana Studio java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM at org.eclipse.swt.internal.Library.loadLibrary(Library.java:182) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:159) at org.eclipse.swt.internal.C.<clinit>(C.java:21) .... at org.eclipse.equinox.launcher.Main.main(Main.java:1287) The error [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)] can apparently be fixed by installing XULRunner (which I already had) and then setting the MOZILLA_FIVE_HOME enviornement variable to point to your xulrunner installation directory with  'export MOZILLA_FIVE_HOME=/usr/lib64/xul-runner-1.9.1/ (aptana forums). Once that's done, I get another error:

(Build 1.5.0.25497) [ERROR] Unable to determine current running state of Aptana Studio org.eclipse.swt.SWTError: No more handles [MOZILLA_FIVE_HOME='/usr/lib64/xulrunner-1.9.1/'] (java.lang.UnsatisfiedLinkError: no swt-mozilla-gtk-3550 or swt-mozilla-gtk in swt. library.path, java.library.path or the jar file) at org.eclipse.swt.SWT.error(SWT.java:3910) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:514) ... at org.eclipse.equinox.launcher.Main.run(Main.java:1311) Caused by: java.lang.UnsatisfiedLinkError: no swt-mozilla-gtk-3550 or swt-mozilla-gtk in swt.library.path, java.library.path or the jar file at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254) Since SWT (Standard Widget Toolkit) is something that you associate with Eclipse, I thought, I would install the eclipse-swt rpm. Unfortunately it didn't solve the issue so I went ahead and installed the full eclipse IDE. In the meantime, on my other machine (thanks VNC), I switched the JVM to a 32 bit version (not with /etc/alternatives but just by setting the JAVA_HOME and PATH enviorenmental variables) and tried running aptana again now both machines produce the identical error message.  So I guess the only difference between the two at the start is that I had switched to a 32 bit JVM on one of them and completely forgotten about it. While doing this, I revisited aptana.com to see if there might be anything in the support forums. What I did find is that I had downloaded the wrong file! yep. I had downloaded a 32bit version while there is a 64 bit version also available! serves me right!

comments powered by Disqus