Note: You are currently viewing documentation for Moodle 3.4. Up-to-date documentation for the latest stable version of Moodle is likely available here: Setting up Eclipse.

Development talk:Setting up Eclipse

From MoodleDocs

Really nice work, Tim, thanks! I've been through and I'm trying it out. Martin Dougiamas 09:05, 5 September 2006 (CDT)


The stuff about changing editors under General -> Editors -> File Associations doesn't work any more if an Eclipse plugin has 'locked' a file type or content type. Not sure how to fix this --Andy Baker 06:40, 28 November 2006 (CST)

Hopefully it will be the PHP plugin, and it will have locked *.php to the setting you want anyway. If not, can you tell us exactly what you are seeing.Tim Hunt 04:24, 29 November 2006 (CST)

Problems with Ubuntu 6.10...

I'd really like to switch completely to Linux and Eclipse on my Moodle developments. However, I can't get the PHPEclipse plug-in to work with Eclipse 3.2 that came with Ubuntu 6.10. After the Eclipse restart required by the "add . to the include path" tweak, the "PHPEclipse stuff" is gone from the menus (forgot what it said), and when I try to open a PHP file in Eclipse I get: "Failed to execute runnable (java.lang.NoClassDefFoundError: net.sourceforge.phpeclipse.phpeditor.PHPUnitEditor)" and "Unhandled event loop exception"... Going to Google around a bit, but there seems to be a lot of other issues with the JVM also: Eclipse crashed when I tried to search the help, for example. --Samuli Karevaara 04:07, 20 December 2006 (CST)

Just reporting that now the error message has changed to "Problems occurred when invoking code from plug-in: "org.eclipse.jface"." or I was reading the wrong part of the error log before... --Samuli Karevaara 04:11, 20 December 2006 (CST)
One headache later I was able to get Eclipse to open the PHP files. Apparently it was about the Java Runtime Environment version after all. I had "sun-java5-bin : Sun Java(TM) Runtime Environment (JRE) 5.0" package installed but it didn't help. After completely removing everything "Java 1.4" ("j2re1.4" and friends) and upgrading "libgjc" packages I got it to work. I reeeeally not a friend of Java versioning and library packaging! --Samuli Karevaara 06:05, 20 December 2006 (CST)