List of eclipse plugins I've found helpful:
getting eclipse installed on centos:
http://www.if-not-true-then-false.com/2010/linux-install-eclipse-on-fedora-centos-red-hat-rhel/
Included in Eclipse releases
Juno Releases: http://download.eclipse.org/releases/juno/
Juno Updates: http://download.eclipse.org/eclipse/updates/4.2
Kepler Releases: http://download.eclipse.org/releases/kepler
Kepler Updates: http://download.eclipse.org/eclipse/updates/4.3
Not included in Eclipse releases:
Android Development Toolkit (ADT): https://dl-ssl.google.com/android/eclipse/ aptana studio3: http://download.aptana.com/studio3/plugin/install
checkstyle: http://eclipse-cs.sf.net/update
eCobertura:http://ecobertura.johoop.de/update
FindBugs:http://findbugs.cs.umd.edu/eclipse
PMD: http://pmd.sourceforge.net/eclipse
subclipse: http://subclipse.tigris.org/update_1.8.x (if I need to go back to svn)
Cucumber-JVM: http://cucumber.github.com/cucumber-eclipse/update-site (mostly used for gherkin .feature file syntax highlighting; I use Spinach in a Ruby stack for running the tests)
Friday, June 20, 2014
Friday, May 2, 2014
Speeding up file open/close in Eclipse 4.3(Kepler) on CentOS 6.5
I recently started a new job, and have been using CentOS 6.5 for my laptop while working as a QA Automation engineer. One of the issues I have run into is that eclipse (main IDE that I use) was taking a long time to both open and close files.
Come to find out that a bug that was initially reported in 2008 is still wreaking havok, namely that gtk+ hangs when looking for network printers using CUPS. This is significant because it doesn't just affect eclipse, but has also been reported to affect firefox, openoffice/LibreOffice, and other applications where you would want to print.
If you want to confirm that this affects you, start eclipse with the following arguements:
eclipse -vmargs -Dorg.eclipse.swt.internal.gtk.disablePrinting
then, open and close files in eclipse and observe performance. For me, files were taking approx 10-30 seconds to open, and up to 30 seconds to close, for *every file*. Running with this option dropped the open/close time to <= 5 sec per file.
Since this impacts more than just eclipse, I wanted to make sure this was resolved on my system. The best workaround I have found is the following, mentioned at the debian bug report listed below. Steps are as follows:
after this, I was able to open eclipse as normal, without the -vmargs argument and without the delay in opening/closing files. Less time waiting on the computer, more time being productive. :-)
see the links below if you are interested in the nitty gritty.
debian bug report that lists work around:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594997
eclipse bug report of the issue with the eclipse vmargs workaround
https://bugs.eclipse.org/bugs/show_bug.cgi?id=275072
linked eclipse bug with more info:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215234
eclipse faq entry with short discussion of issue:
http://www.eclipse.org/swt/faq.php#printOnGTKHangs
Come to find out that a bug that was initially reported in 2008 is still wreaking havok, namely that gtk+ hangs when looking for network printers using CUPS. This is significant because it doesn't just affect eclipse, but has also been reported to affect firefox, openoffice/LibreOffice, and other applications where you would want to print.
If you want to confirm that this affects you, start eclipse with the following arguements:
eclipse -vmargs -Dorg.eclipse.swt.internal.gtk.disablePrinting
then, open and close files in eclipse and observe performance. For me, files were taking approx 10-30 seconds to open, and up to 30 seconds to close, for *every file*. Running with this option dropped the open/close time to <= 5 sec per file.
Since this impacts more than just eclipse, I wanted to make sure this was resolved on my system. The best workaround I have found is the following, mentioned at the debian bug report listed below. Steps are as follows:
- sudo vi /etc/cups/cupsd.conf
- comment out "Listen /var/run/cups/cups.sock"
- sudo vi /etc/cups/client.conf
- add "ServerName 127.0.0.1"
- sudo service cups restart
after this, I was able to open eclipse as normal, without the -vmargs argument and without the delay in opening/closing files. Less time waiting on the computer, more time being productive. :-)
see the links below if you are interested in the nitty gritty.
debian bug report that lists work around:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594997
eclipse bug report of the issue with the eclipse vmargs workaround
https://bugs.eclipse.org/bugs/show_bug.cgi?id=275072
linked eclipse bug with more info:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215234
eclipse faq entry with short discussion of issue:
http://www.eclipse.org/swt/faq.php#printOnGTKHangs
Subscribe to:
Posts (Atom)