- Install From Eclipse Marketplace - See also this screencast.
- Install From Update Site
- Install From Update Site Zip
- Install From Update Site (Scripted)
- Why Eclipse 3.7.2?
Installation From Eclipse Marketplace
1. First, download the correct version of Eclipse for your platform which is compatible with the version of JBoss Tools you plan to install. We recommend you start with the Eclipse 3.7.2 (Indigo SR2) IDE for Java EE Developers in order to install JBoss Tools 3.3 (less dependencies to download). If no bundle is available for your platform, or if you would prefer a smaller download, choose the Eclipse 3.7.2 Platform Runtime Binary - Eclipse will then download only the bare essentials needed for JBoss Tools. Fedora users can simply `
yum install eclipse-platform`.
- Eclipse 3.7.2 Indigo Bundles (including Eclipse 3.7.2 (Indigo SR2) IDE for Java EE Developers)
- Other Versions, Platforms, Options
2. Next, unpack Eclipse somewhere on your drive, eg., ~/eclipse or c:\eclipse
3. If you do not already have Java 6 installed and in your path, download and install that. Fedora users, `
yum install java-1.6.0-openjdk-devel`. Note that gcj/gij is not supported.
4. Double-click the Eclipse icon, or open a terminal and run `
~/eclipse/eclipse -vm /path/to/bin/java`. See also more startup options.
5. When Eclipse starts, go to
Help > Eclipse Marketplace..., then search for "
jboss tools". Click the
Install... button for JBoss Tools (Indigo).
7. JBoss Central also provides you a way to install optional JBoss Tools & third party extras. Simply select the Software/Update tab, then select the features you'd like to install, and restart when prompted.
Installation From Update Site
If you prefer to install individual components of JBoss Tools, you can instead install from an update site.
1. As above, you will need to first download the correct version of Eclipse for your platform, unpack it, install Java 6, and launch Eclipse.
2. When Eclipse starts, go to
3. Paste in the URL of the update site you've chosen, such as:
4. Alternatively, if you prefer to install from an offline update site zip, you can download one and use that instead of a remote http URL as in the screenshot above.
a) Download an Update Site Zip, but DO NOT UNZIP IT.
b) As in step 5 above, when Eclipse starts, go to Help > Install New Software... > Add... However, in this case you should press the Archive... button and browse for the update site zip you downloaded.
If Eclipse crashes during an install, just restart and try again. Launching Eclipse with a different JDK, or giving Eclipse more memory may also help.
6. If you encounter problems resolving dependencies, you can click 'Available Software Sites' and manually add or enable missing sites. You can also import the list of required sites from a bookmarks.xml.
7. After fetching all the features and plugins for installation, you will be prompted that your selection contains unsigned jars. This is normal, and should not be seen as an "unsafe" installation. Simply accept the warning and continue.
8. Install. Restart when prompted. You should see JBoss Central when Eclipse starts, which will provide you news about JBoss Tools and other products, and a way to install optional JBoss Tools & third party extras. Simply select the Software/Update tab, then select the features you'd like to install, and restart when prompted.
9. If the install gets stuck on a particular jar download (bandwidth saturation, slow mirror, etc.), you can shut down Eclipse and try again. Ignore any errors you get when starting the second time - a completed install should resolve them so that when you restart the third time you will be ready to go.
Installation From Update Site Zip (Scripted)
- installJBossTools.sh - wrapper for Ant script w/ usage examples (Linux or Mac OSX)
- installJBossTools.cmd - wrapper for Ant script w/ usage examples (Windows)
- installJBossTools.xml - Ant script, runs p2 director to install specific plugins &/or features, or else everything in the zip
Why Eclipse 3.7.2?
When JBoss Tools 3.3 is installed on 3.7.0 or 3.7.1 with Web Tools 3.3.0 or 3.3.1 these known issues are present: