64 Bit users have a little more work to do, but the process is not too difficult. First, we have to download the relevant packages, and all the dependencies:

• Eclipse gtk 3.5M6 200903130100 (64 Bit)
• PDT 2.1.0M6 Runtime
• EMF 2.5.0M6 S200903161215
• DLTK (Core) R1.0 1.0M6 200903161640
• DLTK (RSE) R1.0 1.0M6 200903161640
• GEF 3.5.0M6 S200903161602
• WTP (WST) 20090318020101 R3.1 3.1M6
• XSD 2.5.0M6 S200903161215

I downloaded them all to a directory called “Galileo” on my Desktop. The rest of the process uses the command line, so open up a Terminal, and navigate to the directory containing the downloaded files:

cd ~/Desktop/Galileo

The first task is to extract the main Eclipse package, and optionally move it to a new home – I chose to install it in ~/galileo/eclipse

tar -zxvf eclipse-SDK-3.5M6-linux-gtk-x86_64.tar.gz
mkdir /home/[USERNAME]/galileo
mv eclipse /home/[USERNAME]/galileo

Eclipse has utilised the p2 Installer, and a “dropins” directory – which is scanned by the p2 Installer whenever Eclipse is executed – since Ganymede 3.4M6. If p2 finds any Features or Plugins, they are installed upon startup. The p2 Installer also allows placing plugins into their own directory structures within the dropins directory, making installing, organising and testing plugins much easier. Of course, this isn’t as easy as using the Update Manager, but it’s very convenient for our purposes of testing pre-release plugins, since they can easily be deleted/upgraded etc. Anyway, I digress – my original point was that we need to extract, and organise each of the packages downloaded above, then move them into the dropins directory:

DLTK Core:

cd ~/Desktop/galileo
unzip dltk-core-sdk-S-1.0M6-200903161640-incubation.zip
mkdir dltk-core & mv eclipse/ dltk-core

DLTK RSE:

unzip dltk-rse-sdk-S-1.0M6-200903161640-incubation.zip
mkdir dltk-rse & mv eclipse/ dltk-rse

EMF:

unzip emf-runtime-2.5.0M6.zip
mkdir emf & mv eclipse/ emf

GEF:

unzip GEF-SDK-3.5.0M6.zip
mkdir gef & mv eclipse/ gef

PDT:

unzip pdt-runtime-2.1.0M6.zip
mkdir pdt & mv eclipse/ pdt

WTP-WST:

unzip wtp-wst-sdk-S-3.1M6-20090318020101.zip
mkdir wtp & mv eclipse/ wtp

XSD:

unzip xsd-runtime-2.5.0M6.zip
mkdir xsd & mv eclipse/ xsd

Finally, we need to move all these new directories containing the plugins, to the Eclipse dropins directory:

mv dltk-core dltk-rse emf gef pdt wtp xsd /home/[USERNAME]/galileo/eclipse/dropins/

That’s the installation complete. We now just need to run Eclipse with the -clean option. This may take a while as p2 scans the dropind watch directory for the new plugins:

cd /home/[USERNAME]/galileo/eclipse
./eclipse -clean

Since it’s the first time we’re running Eclipse, it’ll also ask where the Workspace directory is located. I just chose /home/[USERNAME]/galileo/workspace to keep everything together.

Once Eclipse is loaded, click the “Workbench” button, then go to the Window -> Open Perspective -> Other menu, and select PHP.

The same method can be used to install and test the Nightly Builds of PDT 2.1 – just visit http://www.eclipse.org/pdt/downloads, expand the latest link under the 2.1.0 Nightly Builds heading, download the latest build and the required dependencies, and install using the same methods outlined here.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Getting JRE set up and Ready (Optional)

If you’d like to set up 64 Bit (or 32 Bit) JRE to run Eclipse, follow these instructions.

Installing the Base: Eclipse 3.4 (Ganymede) JEE

First, I downloaded the 64 Bit version of Eclipse IDE for Java EE Developers to my desktop (32 Bit version here). Once downloaded, I extracted the archive, then moved the files to /opt:

cd ~/Desktop
tar -zxvf eclipse-jee-ganymede-SR1-linux-gtk-x86_64.tar.gz
sudo mv eclipse /opt

For 32 Bit:

cd ~/Desktop
tar -zxvf eclipse-jee-ganymede-SR1-linux-gtk.tar.gz
sudo mv eclipse /opt

Installing PDT 2

Simple so far. Once moved (installed), I ran Eclipse for the first time from the command line:

cd /opt/eclipse
./eclipse

and selected a workspace within my home directory once prompted. From here, installing PDT 2 is an easy task – adding two sites to the Update Manager (far easier in Ganymede than Europa), and letting Eclipse to the rest. Once Eclipse had started, I went to Help -> Software Updates. The Software Updates and Add-ons window appeared, and I navigated to the Available Software tab. From there, I clicked the “Manage Sites” button, followed by “Add” once the Site Manager appeared. The only additional prerequisite to install for PDT is the Dynamic Languages Toolkit, or DLTK. So, I added:

http://download.eclipse.org/technology/dltk/updates-dev/1.0/

in the Dialog, and clicked OK. I then needed to add the PDT update site, so clicked add, and pasted:

http://download.eclipse.org/tools/pdt/updates/2.0/interim/

Click OK to close the Available Sites Manager. The rest is just as easy – two new sites should appear in the Available Software sites list. So, I expanded the DLTK site (the small triangle to the left of the site name), then the Dynamic Languages Toolkit option, and checked “Dynamic Languages Toolkit – Core Frameworks (Incubation)”, from the top of the list. Finally, I repeated the process with the PDT Update site – expanded PDT Update Site -> PDT SDK 2.0.0 and checked “PDT Runtime Feature” from the list. That’s it. Click Install and follow the prompts.

Once installed, Eclipse recommends restarting the application. Accept, restart, and enjoy a shiny new PHP IDE, with PDT 2.

Setting Up the Environment

Once Eclipse Ganymede has reloaded, click on the Workspace icon to open the IDE workspace for the first time. The default Perspective is JEE. To change this, go to Window -> Open Perspective -> Other, then scroll down and select PHP. Other Views, relating to other plugins can be inserted into this perspective, and the perspective saved for future use. Personally, I like to add the SQL Development views, and MyLin, for live access to Bugzilla (Window -> Sow View -> Other).

A new PHP Project can be started by right clicking in Project Explorer (left window pane), and selecting New PHP Project (“Other” may need selecting on the first run, followed by navigating to and selecting PHP Project from the list).

That’s it. Far easier than previous versions, and much less effort required in the process! We like that.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Update, 16/01/09: This Guide has been superseded by “Full 64 Bit (or 32 Bit) Web Development and PHP/MySQL IDE with Eclipse 3.4 Ganymede and PDT 2“, but will be left here for reference, history, and so on… PDT is MUCH easier to install now

I’ve been checking out the recently released Eclipse 3.4 (Ganymede), and so far so good. I’ve managed to get PDT (for PHP Development) and SQL Explorer installed and running successfully, so I’ll be doing some testing to see how it compares to Europa, which I have been using for some time. Thankfully, installing plugins is much easier with Ganymede – this is how I got it set up an configured.

IMPORTANT NOTE: This installation configuration currently relies on Integration builds of both PDT and DLTK, since the current Stable builds of each are not currently supported under Eclipse 3.4. I will update this tutorial as support becomes available, but if you are not comfortable installing Integration builds, please see my previous tutorial on setting up a PHP IDE in Eclipse Europa: “64 Bit Eclipse: Linux Installation, including PDT, WTP (WST), ATF, and MySQL (SQL Explorer Plugin)“.

Install Eclipse

Installing Eclipse is a pretty easy task – just head over to http://www.eclipse.org/downloads and download the latest version of “Eclipse Classic” (direct link to 64 bit version). I downloaded the file to my desktop, and once finished, opened up a Terminal window, extracted the archive, and installed Eclipse into the /opt directory:

cd ~/Desktop
tar -zxvf eclipse-SDK-3.4-linux-gtk-x86_64.tar.gz
sudo mv eclipse /opt/ganymede

I installed into /opt/ganymede since I already have Europa installed in /opt/eclipse.

That’s all there is to installing Eclipse. It can be run (for now) via the Terminal:

cd /opt/ganymede
./eclipse

Installing PDT

As mentioned above, the latest Stable build of PDT is not yet supported in Eclipse 3.4, and since only PDT 1.0.x is available via the Update Site, it’s necessary to download the 2.0.x Integration Build from the PDT Website (see this thread at pdt-dev for more information). The same goes for DLTK (Dynamic Languages Toolkit) upon which PDT depends – only the Integration Build may be installed with Ganymede.

Firstly I downloaded DLTK, from http://download.eclipse.org/technology/dltk/downloads – click on the Integration Build download link, and grab the Core Frameworks archive (direct link to current version – Integration Builds are likely to change frequently, so best to visit the main doanload page). Next, grab the PDT archive from http://download.eclipse.org/tools/pdt/downloads/ (click on the 2.0.0 Integration Build link, then grab the PDT Runtime archive – direct link). Don’t worry about the requirements and handy extras.

Once downloaded, again to my Desktop, I created a couple of temporary directories, and unziped both archives into their respective new homes:

mkdir pdt dltk
mv org.eclipse.php_feature-I20080722.zip pdt
cd pdt
unzip org.eclipse.php_feature-I20080722.zip pdt
cd ~/Desktop
mv dltk-core-I-I200807291021-200807291021-incubation.zip dltk
cd dltk
unzip dltk-core-I-I200807291021-200807291021-incubation.zip

Now the Eclipse Update manager can be pointed to these “local sites”. I fired up Eclipse once again, and navigated to the Update Manager: Help -> Software Updates. Once open, I clicked on the Available Software tab, and added the new sites – click on Add Site, click Local, and navigate to ~/Desktop/pdt/eclipse. Click OK, and repeat for ~/Desktop/dltk/eclipse. Now there should be two more sites (“/home/username/Desktop/pdt/eclipse” and “/home/username/Desktop/dltk/eclipse”) in addition to “Eclipse Project Update Site” and “Ganymede” (or “http://download.eclipse.org/releases/ganymede”). Expand each of the two new sites, and select the lowest leaf in each tree – “PDT Feature” and “Dynamic Languages Toolkit”.

PDT is also dependent upon the Graphical Editing Framework (GEF), so expand the Ganymede tree, then “Graphical Editors and Frameworks” and select the “Graphical Editing Framework GEF” option.

Don’t click “Install” quite yet – there are a few other additional things to select for a full Web Application Development IDE.

Web Application stuff

Expand the main Ganymede tree, and “Web and Java EE Dvelopment”. I personally selected:

• Eclipse XML Editors and Tools
• Javascript Developer Tools
• Web Developer Tools
• Web Page Editor

You may want more, or less. Almost there…

Database Integration

Expand Database Development, and select Data Tools Platform Enablement and Data Tools Platform SQL Development. These are required for setting up a connection to MySQL later.

OK, click Install! Go and make a brew, or coffee – this may take some time.

Once everything has been downloaded and installed, restart Eclipse.

SQL Explorer Plugin

I find SQL Explorer is a great little plugin to use as a DB GUI. To install it, I downloaded the latest version to my Desktop, and extracted the files.

cd ~/Desktop
mkdir sqlexplorer
mv sqlexplorer_plugin-3.5.0.RC5.zip sqlexplorer
cd sqlexplorer
unzip sqlexplorer_plugin-3.5.0.RC5.zip

As with the PDT and DLTK plugins, to install is just a simple case of adding a new Local site to the Eclipse Update Manager, and selecting the plugin to install. So, open up the Update Manager – Help -> Software Updates, and select the Available Software tab. Add new site, click Local, navigate to ~/Desktop/sqlexplorer, click OK, etc. Once the site is added, expand the new SQL Explorer, select the lowest level leaf, and click install.

Once installed, restart Eclipse. Some configuration is still required to get SQL Explorer linked up to a MySQL Database, which I have covered in a previous tutorial: Eclipse PDT and MySQL – SQL Explorer Plugin. It’s pretty simple, and just involves downloading the Java Connector for MySQL, and pointing Eclipse to it.

ATF (AJAX Toolkit)

Unfortunately, ATF is not yet supported in Ganymede – I’m keeping track of it, however, and will update this tutorial as soon as support is available. In the mean time, check out the current status at atf-dev.

Debugging PHP with Xdebug

The information in my previous tutorial, Debugging PHP Applications with Xdebug and Eclipse PDT, can still be applied to Ganymede.

Hope that helps.

References

1. http://wiki.eclipse.org/PDT/Installation#Eclipse_3.4_.2F_Ganymede_.2F_PDT_1
2. http://www.mail-archive.com/pdt-dev@eclipse.org
3. http://www.mail-archive.com/atf-dev@eclipse.org

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

AnyEdit tools is easy to install – in Eclipse, go to Help -> Software Updates -> Find and Install and select the “Search for ne features to install” option. Click on “New Remote Site”, and add “AnyEdit tools” as the Name, and http://andrei.gmxhome.de/eclipse/ as the URL and click OK. Tick the box next to the new site, and click Finish. Once the update site has been contacted, and the plugin list retrieved, expand the AnyEdit tools -> Eclipse 3.3 plugins, and select AnyEditTools 2.0.2. Click Next, accept the agreement, Next, Next, Finish. Once dowloaded, the Update Manager asks to verify the installation – click Install, and that’s it. Eclipse needs restarting to activate the plugin.

Related posts:

1. Quickly archive multiple directories into separate archive files I recently needed to quickly archive several hundred directories, and...

Related posts brought to you by Yet Another Related Posts Plugin.

Xdebug is a fantastic PHP extension, which is written by one of the PHP Core Developers, Derick Rethans. The current version is 2.0.3, and I set about installing it on my system, and integrating it into Eclipse PDT today.

Xdebug can be installed in a few different ways – by downloading the binaries from the site, compiling the source, or via PECL:

sudo pecl install xdebug

Some days, I just prefer to download compile the source, as it gives me more of an understanding of what is being installed and where, and this is one of those days:

cd ~/
mkdir xdebug
cd xdebug
wget http://www.xdebug.org/link.php?url=xdebug203
tar -zxvf xdebug-2.0.3.tgz
cd xdebug-2.0.3

The packages phpize and php-config are required to install Xdebug, and can be obtained by installing the relevant PHP development packages:

sudo apt-get install php4-dev

or

sudo apt-get install php5-dev

depending on the PHP version installed. After unzipping the Xdebug source, I ran

phpize

which output:

PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519

I then checked this against the table at http://www.xdebug.org/docs/install#phpize to see if my PHP version (5.2.3) was compatible with Xdebug – it matched up to the table’s 5.2.x PHP version row, so I went ahead and installed:

./configure --enable-xdebug --with-php-config=/usr/bin/php-config
make

which created a file xdebug.so in the modules subdirectory. This file needs to be copied (or moved) to the PHP Extension directory, which on my system is in /usr/lib/php5/20060613/. An easy way to find the PHP extension directory is to run:

locate mysql.so

ok, so I copied the xdebug.so to the extension directory:

sudo cp modules/xdebug.so /usr/lib/php5/20060613/

So far so good. Now PHP needs to be told about the extension, and to load it. This can be done by adding

zend_extension="/usr/lib/php5/20060613/xdebug.so"

to the php.ini file. However, on my Ubuntu system, the PHP extensions are activated by adding an .ini file to the /etc/php5/apache2/conf.d directory, for each extension installed. The .ini file is the extension_name.ini, so I created a file called xdebug.ini:

cd /etc/php5/apache2/conf.d
gksu gedit xdebug.ini

which for now, contains a single line:

zend_extension="/usr/lib/php5/20060613/xdebug.so"

After restarting the Apache server

sudo /etc/init.d/apache2 restart

I created a file called test.php in my Web Root directory, containing a call to the phpinfo() function:

<?php
phpinfo();
?>

and pointed my browser to http://localhost/test.php. Just before the “PHP Credits” section, is a small box containing information on Zend – and now, with a successful Xdebug installation, additional information on Xdebug:

The same information can be found by opening a Terminal and running

php -m

to output the loaded modules, and towards the end of the output, you should see

[Zend Modules]
Xdebug

alternatively, run

php -i | grep Xdebug

and if Xdebug has been installed successfully, you should see

with Xdebug v2.0.3, Copyright (c) 2002-2007, by Derick Rethans

Now, Xdebug needs to be enabled before any scripts can be debugged! So, in the php.ini file (or in my case, the newly created /etc/php5/apache2/conf.d/xdebug.ini file) I added the lines:

xdebug.remote_enable=On
xdebug.remote_host="localhost"
xdebug.remote_port=9000
xdebug.remote_handler="dbgp"

and restarted Apache again:

sudo /etc/init.d/apache2 restart

running

php -i | grep xdebug

in the Terminal, or using the test.php file containing phpinfo() shows that the new settings are being used, and Xdebug is active and running.

Configuring Eclipse PDT:

Setting up Eclipse PDT to use the Xdebug extension is pretty simple. In Eclipse PDT, I opened Window -> Preferences, then clicked on PHP, expanded the tree, and selected Debug. I Chose Xdebug from the pull down menu for the PHP Debugger, the “Default PHP Server” (should already be set to localhost), and then created a new PHP Executable option by clicking on the PHP Executables link next to the PHP Executable pull down menu.

In the PHP Executables dialog, I Clicked Add, filled in the name (PHP with XDebug), and entered the path to the PHP executable – on my system this is /usr/bin/php but if you don’t know, then in a terminal, run

which php

to find out where the php command is run from. I also entered the location of php.ini – again, on my system, this is /etc/php5/apache2/php.ini – and selected XDebug as the PHP debugger:

Clicked OK, then went back to the PHP -> Debug preferences screen, and selected the PHP Executable just created in the PHP Executable pull down. Finally, in the Debug -> Workbench Options option in the left, I selected “Never” for the “allow multiple debug sessions” option, since Xdebug does not support them.

Finally, I needed to set the Default Web Browser in Eclipse, to that when I debug a script, the output is sent to Firefox. Again in Preferences, I navigated to General -> Web Browser, and clicked “New”. It’s pretty straight forward stuff – entering a name and location – Firefox, and /usr/bin/firefox. Again, if you don’t know the location of the firefox binary, in a terminal run:

which firefox

With this done, and the preferences saved, I can now debug my scripts using Xdebug!

References:

http://www.xdebug.org/docs/install
http://www.eclipse.org/pdt/documents/XDebugGuide.pdf
http://devzone.zend.com/article/2803-Introducing-xdebug

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

NOTE, 04/08/08: This tutorial covers Eclipse Europa. If you would like to install the latest version of Eclipse 3.4 Ganymede, with PDT and SQL Explorer, take a look at my latest Tutorial: “64 Bit Eclipse 3.4 (Ganymede) IDE with PDT and SQL Explorer – Full PHP/MySQL Web Application IDE“.

I had tried once before to install the x64 (64 Bit) version of Eclipse IDE, about 8 months ago, but found it to be somewhat buggy and unstable. In the interim, I’ve been using the 32 Bit version of Eclipse PDT for my development stuff. Earlier this year (21/02/08) a new version of Eclipse 64 Bit was released, so I gave it a go today. So far, so good!

Unfortunately, there’s no 64 Bit PDT all-in-one, but I managed to install a 64 Bit equivalent by cobbling together the relevant packages available by using the Eclipse Update Manager system, after initially installing the latest version of Eclipse Classic 3.3.2 64 Bit.

I wanted to keep everything (or as much as possible) 64 Bit, so I also download and installed the 64 Bit JRE, which can be downloaded here (or use the direct link to the bin file). The method for installing the 64 Bit JRE is the same as the 32 Bit version – after the file downloaded to my desktop, I opened up a new Terminal Window (Applications -> Accessories -> Terminal), traversed to the directory I wanted to install it into, moved the file, made it executable, and ran it to install:

cd /usr/java
sudo mkdir 64
cd 64
sudo mv ~/Desktop/jdk-6u5-linux-x64.bin /usr/java/64/
sudo chmod a+x jdk-6u5-linux-x64.bin
sudo ./jdk-6u5-linux-x64.bin

If the “java” directory doesn’t exist, it needs to be created first:

sudo mkdir /usr/java

listing the directory

ls

should return

jre1.6.0_05

which is the directory containing the necessary Java binaries.

As with my previous 32 Bit installation, I wanted Eclipse to be installed in the /opt directory:

cd /opt
sudo mv ~/Desktop/eclipse-SDK-3.3.2-linux-gtk-x86_64.tar.gz /opt
sudo tar -zxvf eclipse-SDK-3.3.2-linux-gtk-x86_64.tar.gz

then rename the eclipse directory:

sudo mv eclipse eclipse64

I also needed to get the newly installed Eclipse to run with the newly installed JRE – by default, the eclipse executable in the directory will try and detect Java and use whatever it finds, so I created a shell script:

cd eclipse64
sudo gksu gedit eclipse.sh

containing the following:

#!/bin/bash
PATH=/usr/java/64/jre1.6.0_05/bin:$PATH
/opt/eclipse64/eclipse

Now instead of running the eclipse executable, I run eclipse.sh (make sure it’s executable)

sudo chmod 755 eclipse.sh

before running

/opt/eclipse64/eclipse.sh

PDT and WTP Plugins

The first time I ran the new 64 Bit version, everything went well – it was fast, and seemed stable, so I went ahead and started installing all the additional plugins I needed (and still need…). Goto Help -> Software Updates -> Find and Install, and select “Search for new features to install”.Click on “New Remote Site” for each of the following:

• Name: PDT, URL: http://download.eclipse.org/tools/pdt/updates/
• Name: WTP, URL: http://download.eclipse.org/webtools/updates/
• Name: GEF, URL: http://www.eclipse.org/gef/updates/
• Name: EMF, IRL: http://www.eclipse.org/modeling/emf/updates/

Actually, there are only a couple of components required from the GEF (Graphical Editing Framework) and EMF (Eclipse Modeling Framework) packages to satisfy dependencies – WTP (Web Tools Platform) requires a package from GEF, and GEF from EMF…

After adding these, click on Finish – the Update Manager will then query any mirrors for the latest versions of the plugins. Once it has finished, a dialog appears, where it is possible to select the plugins to download and install. First, I selected PDT – the Update Manager then informed me that PDT requires files from WTP, so I tried clicking the “Select Requires” button, hoping that it would sort out the dependencies on my behalf. Unfortunately, nothing happened… So, I selected WTP manually, then expanded GEF -> Eclipse SDK R3.3.1 and Selected Graphical Editing Framework 3.3.1v20070814, then expanded EMF -> EMF SDK 2.3.2 and selected Eclipse Modeling Framework (EMF) – org.eclipse.emf.ecore 2.3.2v200802051830… I could then click “Select Required” to get the last few residual required dependencies… Phew…

Actualy, it still bugged me for dependencies for Java Persistence API contained in WTP, but by that stage I really couldn’t be arsed going through the process of adding more stuff to the Update Manager and potentially having to search for further dependencies, so I just deselected the three Java Persistence API files contained in WTP.

OK, with the dependencies sorted, I clicked Next, accepted the agreements, finished, and went to make, and drink a brew (that’s Tea) while the Update Manager downloaded and installed the requested stuff.

MySQL: SQL Explorer Plugin

Once everything had downloaded and installed, I restarted Eclipse. Everything looked good! Great, in fact. But I also wanted to install a few more plugins, including the MySQL SQL Explorer Plugin – which additionally requires, and depends on Eclipse DTP (Data Tools Project). Eclipse DTP has to be downloaded and installed manually, since there is no automated Update Site. So, I downloaded dtp_1.5.2_022008.zip to my Desktop, and set about extracting and installing the files:

cd ~/Desktop
mkdir DTP
mv dtp_1.5.2_022008.zip DTP
cd DTP
unzip dtp_1.5.2_022008.zip
cd eclipse
sudo cp -R features plugins /opt/eclipse64

If Eclipse is open, restart it. With the DTP installed, I could set about installing the SQL Explorer Plugin. The instructions for installing and configuring the SQL Explorer Plugin can be found in my previous article – Eclipse PDT and MySQL – SQL Explorer Plugin, since I don’t want to regurgitate information, just follow the link if you need to install it, and come back when it’s done.

Note: Actually, now I had the DTP installed, I could download and install the additional Java Persistence API in WTP! Same method: Update Manager, select WTP etcetera, etcetera…

ATF: AJAX Framework Toolkit

Once the SQL Explorer Plugin was installed, I had one final plugin – ATF (the AJAX Toolkit Framework). This can be downloaded as a Site Archive, and the zip file added to Eclipse’s Update Manager. Once downloaded, I opened the Update Manager in Eclipse (Help -> Software Updates -> Find and Install), and clicked on “New Archived Site”, to add a new locally archived site, calling it ATF, and pointing it to the freshly downloaded atf-incubation-SiteArchive-0.2.3M4-v200709141050.zip file. I discovered, however, that the site.xml file contained within the zipped site archive is somewhat out of date and the pointers within are directed to the wrong download locations, so I had to manually locate the additional dependent plugins – Mozilla XULRunner, and Mozilla JS. They can both be added as New Remote Sites to the Update Manager, by clicking on the “New Remote Site” button, and adding the following information:

• Name: Mozilla JS, URL: http://ftp.mozilla.org/pub/mozilla.org/js/eclipse/
• Name: XULRunner, URL: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/

The previously used EMF plugin is also required to satisfy a couple of dependencies, so I selected the ATF, Mozilla JS, XULRunner, and EMF plugins from the list, and clicked Finish. Once the “updates” were found, I selected XULRunner, Mozilla JS, ATF (I deselected the ATF -> Mozilla JS component though, since an updated version was to be downloaded and installed from the Mozilla Server), and also selected the required EMF components. Click through Next etc. to download and install. Once completed, I restarted Eclipse.

In the Window -> Preferences menu by the way, AJAX toolkits such as Script.aculo.us can be added to the ATF module.

Et Voila! I now have a working Eclipse 64 Bit version up and running! Finally!

Oh, if you want a desktop icon, just create a file on your Desktop called Eclipse.desktop,

cd ~/Desktop
gedit Eclipse.desktop

and add the following:

[Desktop Entry]
Categories=;
Encoding=UTF-8
Exec=/opt/eclipse32/eclipse.sh
Hidden=false
Icon=/opt/eclipse64/icon.xpm
Icon[en_US]=/opt/eclipse64/icon.xpm
Name=Eclipse
Name[en_US]=Eclipse
Terminal=false
Type=Application
Version=1.0

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

phpMyAdmin, MySQL Administrator and MySQL Query Browser can be installed as follows, by the way:

sudo apt-get install phpmyadmin mysql-admin mysql-query-browser

Installing Eclipse SQL Explorer was pretty straight forward – I simply downloaded the archive package from Sourceforge, saved it to a directory in on my desktop (there is also a standalone client available, so be sure to download “Eclipse SQL Explorer [RCP/Plugin]” if you’re setting it up as an Eclipse plugin – here’s a direct link to the latest plugin file), and extracted the files:

cd ~/Desktop/sqlexplorer
unzip sqlexplorer_plugin-3.5.0.RC5.zip


This created two directories (features and plugins) along with two text files. To install the plugin, I just copied the two directories to my Eclipse root installation directory (see my previous post “Eclipse PDT IDE for PHP MySQL 32 Bit install on 64 Bit Ubuntu“), which is /opt/eclipse32

cp -R features plugins /opt/eclipse32/

Notice there was no need to use the sudo command before copying, since my user owns the eclipse32 folder.

Configuring SQL Explorer

Once installed, I also had to do some additional setup before I could configure SQL Explorer to connect to my local MySQL databases via Eclipse – namely, download and install the Java Connector for MySQL (MySQL JDBC Driver), to enable JDBC connections. The latest driver (5.1 at the time of writing) tar.gz file can be downloaded from the MySQL site here.

Once downloaded, I just extracted the files, and entered the new directory:

cd ~/Desktop/mysqljdbc
tar -zxvf mysql-connector-java-5.1.6.tar.gz
cd mysql-connector-java-5.1.6

The important file here (along with the documentation, of course) is the mysql-connector-java-5.1.6-bin.jar file, which is the driver itself. I guess this could be placed anywhere, since we just need to point the SQL Explorer plugin to it when setting it up in Eclipse, but for convenience and tidiness, I moved it to the /usr/share/mysql directory:

sudo cp mysql-connector-java-5.1.6-bin.jar /usr/share/mysql

With the JDBC driver installed, I could set up the Eclipse SQL Explorer plugin. In Eclipse, I went to Window->Preferences and expanded the new SQL Explorer section, highlighting “JDBC Drivers”, then double clicking on “MySQL Driver” to open the MySQL setup dialog:

In the MySQL Driver setup, I had to point the plugin to the MySQL JDBC Driver, by clicking on the “Extra Class Path” tab, and then clicking “Add” to point it to /usr/share/mysql/mysql-connector-java-5.1.6-bin.jar. Once added, clicking on “List Drivers” will bring up the list of available drivers in the “Driver Class Name” pull down menu. Only one is listed, and it just so happens to be the one we need – com.mysql.jdbc.Driver:

Click OK, and the driver is set up! I also clicked the “Set Default” button, since MySQL is currently the only database I connect to. With the Driver set up, I could then set up a connection to my database system. If the “Connections” view is not already available, it has to be selected via the Window->Show View->Other menu, and clicking on the “Connections” view within the “SQL Explorer” folder in this dialog.

With the Connections View available, I could set up the new connection profile, by right clicking in the view and selecting “New Connection Profile”, which opens up a new dialog, in which the new connection data is input:

It was a pretty simple process to create the connection – I just needed to replace the relevant parameters in the JDBC connections string with my connection details, so

jdbc:mysql://<hostname>[<:3306:>]/<dbname>

became

jdbc:mysql://localhost:3306/mydatabase

Entered the DB username and password, gave the connection a name, selected the newly created MySQL Driver, and clicked OK to save the connection. Double clicking the connection name in the Connections View connects to the DB and brings up an SQL window form which Queries may be run. By default, the results are displayed in a small view at the bottom of the main Eclipse IDE window – although, this can be dragged and placed anywhere. There are also several other views available via the Window->Show View->Other menu within the SQL Explorer section to peruse.

The Eclipse SQL Explorer homepage has extensive documentation available, including a cool section on extending the plugin. Maybe I should learn Java too?

That’s all Folks.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Update 12/04/08: I have now successfully installed the x64 version of Eclipse – see 64 Bit Eclipse: Linux Installation, including PDT, WTP (WST), ATF, and MySQL (SQL Explorer Plugin) for a step by step guide, or continue reading this article if you want to install the 32 bit version.

32 Bit installation

I went through several different methods of installing the Eclipse IDE on my Ubuntu system. I tried the obvious first – installing via the Synaptic Package Manager, but found it a bit of a pain to install any plugin packages I downloaded (I also use WST and SqlExplorer in addition to PDT). So, I uninstalled, then tried the 64 Bit version of the SDK (which at the time was pretty buggy, and unstable), in the hope that I’d be able to plug in a 64 Bit version of the PDT, which I soon found doesn’t exist yet! So, I finally settled for installing the 32 Bit version of Eclipse PDT, which enabled me to install the plugins too.

In order to install and run this successfully, I first downloaded the 32 Bit Java Runtime Environment installer “Linux (self-extracting file)” from http://www.java.com/en/download/linux_manual.jsp (or direct link to the file), and saved the jre-6u3-linux-i586.bin to my desktop.

Once the file downloaded, I opened up a Terminal (Applications -> Accessories -> Terminal), and typed

cd /usr/java

(if the java directory doesn’t exist, it need to be created:

sudo mkdir /usr/java
cd /usr/java

I also wanted a 64 bit version of the JRE installing, so within the /usr/java directory, created two more sub directories:

sudo mkdir 32
sudo mkdir 64

then copied the newly downloaded JRE installation file from the desktop to the /usr/java/32 directory, and made the file executable:

cd 32
sudo mv ~/Desktop/jre-6u3-linux-i586.bin /usr/java/32/jre-6u3-linux-i586.bin
sudo chmod a+x jre-6u3-linux-i586.bin

then execute the binary:

sudo ./jre-6u3-linux-i586.bin

Accept the terms, and so on and so forth… When it says “Done”, it’s, well, done!

ls

should return:

jre1.6.0_03

Note: If you download a newer version of JRE, then you’ll need to change the above commands containing “jre-6u3-linux-i586.bin” to “jre-6u<version>-linux-i586.bin” where <version> is 3, 4, 5 etc.!

Now for Eclipse. I downloaded the latest version from http://download.eclipse.org/tools/pdt/downloads/ (the current stable version is R20080103) – I click on the link for the latest release, and downloaded the pdt-all-in-one-R20080103-linux-gtk.tar.gz file to the desktop. Once it finished, I went back to the terminal, and entered the /opt directory, moved the Eclipse package to the /opt directory, and extracted the new files:

cd /opt
sudo mv ~/Desktop/pdt-all-in-one-R20080103-linux-gtk.tar.gz /opt
sudo tar -zxvf pdt-all-in-one-R20080103-linux-gtk.tar.gz

This extracts the Eclipse IDE into a directory called, oddly enough, “eclipse”. However, I’m experimenting with the 64 bit version too, so I changed the directory name to eclipse32:

sudo mv eclipse eclipse32

As it was, Eclipse wouldn’t run, since it doesn’t know where to find the JRE I’d just installed, so, I had to create a small shell script in order for it to run correctly:

cd eclipse32
gksu gedit eclipse.sh

This opened up a text editor, with a blank file called “eclipse.sh”. The shell script is:

#!/bin/bash
PATH=/usr/java/32/jre1.6.0_03/bin:$PATH
/opt/eclipse32/eclipse

PATH=/usr/java/32/jre1.6.0_03/bin:$PATH should point to the bin directory of the previously installed.

The script also needed to be executable:

sudo chmod 755 eclipse.sh

and I also changed the ownership of all the files and directories to my username:

sudo chown -R username:group *

That was pretty much it – I could run Eclipse by opening a Terminal window and running

cd /opt/eclipse32
./eclipse.sh

which got a little tiresome after the first time, so I created a menu item (System -> Preferences -> Main Menu) which pointed to /opt/eclipse32/eclipse.sh, and even included the png Eclipse logo for the icon

Any plugins can be downloaded, and extracted into the relevant directories – or, installed by the Eclipse Update Manager.

I’ve recently written a post on “Eclipse PDT and MySQL – SQL Explorer Plugin“, for anyone who needs to set up MySQL connections in Eclipse.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.