Matthew Woodward // * CFML, Grails, and Java Developer
* Principal IT Specialist, US Senate
* Open BlueDragon Steering Committee Member
* All-Around Geek
UBUNTU_MENUPROXY= /home/mwoodward/sts/STSNote that there is a space after the equals sign. Of course if you're having this issue with another application you'd just substitute the path to that application where I have /home/mwoodward/sts/STS And you can obviously throw this into a launcher script so you don't have to remember to type this every time. I was also having problems with the menus on UltraEdit so I was happy to see this fix resolved those issues as well. With a workaround for this issue I now give the Unity interface a grade of a nice solid B as opposed to the C I gave it in my previous post. There are still some quirks here and there but at least now I can use STS without any issue. I'm always amazed, yet never surprised, at the excellent support available from the community of free software projects. With commercial software you pay for support, and in my experience it isn't very good as a rule, but with free software you have legions of users at the ready to help other users, and you can also pay for commercial support if you so need or desire. What's not to love?
If you use Eclipse and Subclipse, chances are you've see the "Subversion Native Library Not Available" error (see attached pic). Things tend to work fine even if you see that error (at least they did for me), but I finally took the time the other night to get to the bottom of it and fix it in the easiest way possible.
First, do this:sudo apt-get install libsvn-javaNext, do this:
sudo cp /usr/lib/jni/* /usr/libNow I said "easiest way possible" above because you can monkey around with eclipse.ini -VMARGS and all sorts of other nonsense, but chances are none of those solutions will work if you actually want to use a launcher to launch Eclipse.
So do yourself a favor, drop the files where Eclipse expects to find them, and get on with your life. (As you can tell, I spent more time on this than I wanted to, so I'm simply trying to help others avoid this same fate.)
After upgrading to Ubuntu 9.10 (Karmic Koala) some buttons no longer work in Eclipse 3.5. Clicking has no effect but keyboard shortcuts still work.
It looks like Eclipse is doing some nasty stuff advanced hacking in SWT on GTK. This bug is fixed in 3.6M2 but you can work around the issue in Eclipse 3.5 by launching Eclipse through the following small shell script (assuming Eclipse is installed in /opt/eclipse-3.5):
#!/bin/sh export GDK_NATIVE_WINDOWS=1 /opt/eclipse-3.5/eclipse
If you're having this issue it will rear its ugly head when you try to do things like create a new project or add a software repository to your updates list--you'll click the "next" or "OK" button and nothing will happen. Glad there's an easy workaround, this has been driving me nuts all morning!
I finally felt like I was at a point with projects, etc. that I could try CFEclipse this week. When I want to try a new piece of software (or when I switched from the PC to the Mac for example), I always try to give it a real try, meaning I abandon my old tool/program/computer/what have you and only use the new tool for an entire week. So this week I shut down Dreamweaver MX 2004 and fired up CFEclipse to see how it would go.
I have to admit this wasn't my absolute first time using Eclipse, but I'd only really dabbled before or used it when I was doing some Java stuff (for which Dreamweaver is absolutely horrendous). I really love some of the features so I was pretty sure I'd take right to it, but you never know until you cut the cord and only use the new tool.
When I did this one-week trial with a Mac I never went back to a PC and it's looking like this is going to be the case with CFEclipse as well. I kept expecting there would be several "I wish I could do X like I did in Dreamweaver," but it didn't happen once, and there's a lot CFEclipse has going for it over Dreamweaver. I won't go into this in detail since you've probably read about CFEclipse before in other blogs; this entry is more just to serve as one more CFer singing its praises and to be counted amongst the converted.
Couple things I noticed.
That really is pretty much it, believe it or not! The one huge thing I'd love to see that I also know is in the works is the ability to FTP right from the file browser. That's the one thing I miss from Dreamweaver, but the rest of Eclipse is good enough that I'll live without it for a while.
I'll still be using Dreamweaver on my PC for work because we do a lot with Contribute and use Dreamweaver templates pretty heavily, but when I'm doing my own stuff or doing coding that doesn't involve DW templates, CFEclipse has definitely become my main IDE. Time to start digging deeper and seeing what other cool Eclipse plugins there are out there ...
Kudos to Spike and the whole CFEclipse team--keep up the fantastic work!