Installation
- Install From Eclipse Marketplace
- Install From Update Site
- Install From Update Site Zip (Scripted)
- Why Eclipse 4.2.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 4.2.2 (Juno) IDE for Java EE Developers in order to install JBoss Tools 4.0 (less dependencies to download). If no bundle is available for your platform, or if you would prefer a smaller download, choose the Eclipse 4.2.2 Platform Runtime Binary - Eclipse will then download only the bare essentials needed for JBoss Tools. Fedora users can simply `
2. Next, unpack Eclipse somewhere on your drive, eg., ~/eclipse or c:\eclipse 3. If you do not already have Java 6 (or 7) installed and in your path, download and install that. Fedora users, ` 4. Double-click the Eclipse icon, or open a terminal and run ` |
|
6. Restart when prompted. You will see JBoss Central on startup, which will provide you news about JBoss Tools and other products. |
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.
Enjoy!
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 Help > Install New Software...
3. Paste in the URL of the update site you've chosen, such as:
Depending on your network location & speed, you may want to uncheck the checkbox for "Contact all update sites during install to find required software". Doing so should restrict your search to download.jboss.org rather than all the eclipse.org mirrors.
Installation From Update Site Zip (Scripted)
Should you want to install from an Update Site Zip via a script (eg., for easy deployment / testing) you can use the following scripts:
- 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 4.2.2?
While much of JBoss Tools 4.0 will work with Eclipse 4.2.0, we recommend using the latest Eclipse Juno SR2 to take advantage of performance fixes Eclipse 4.2.2.
When JBoss Tools 4.0 is installed on Eclipse 4.2.0 or 4.2.1 (included in Juno R and SR1, respectively) this known issue is present:
- Bug 385272 Very slow response after upgrade to Juno Release. See also Platform UI / Juno Performance Investigation.
However, when using Web Tools 3.4.1 or 3.4.2 (included in Juno SR1 and SR2, respectively), this known issue is present
- Web Tools 3.4.1 introduced a behaviour change (which some might consider a bug) in that it now ignores metadata files such as .project. See JBIDE-13830
If you prefer to use the initial Juno R release (Eclipse 4.2.0, Web Tools 3.4.0) to avoid the Web Tools issue introduced in 3.4.1, you can install the Juno SR1 performance patch from JBoss Tools Central:
