Setup

It is advised that the Eclipse Development Environment and the Target Environment are separated. Here, we will refer to them as SDK and Target respectively.

You can set the whole thing up differently, but this is how I do it.

This setup only make sense if you are developing GenericFX and its derivatives. In particular, this approach assume that you are going to modify so many packages in GenericFX and its derivatives that it make no sense setting the target environment to GenericFX, especially the RCP version. If you only need to modify your own code and not GenericFX, consider setting up the target environment to be the actual GenericFX environment itself.

Other documents:

Required Software

  • Java 1.4. Cannot use Java 1.5.

Procedure

  1. Setup the SDK and Target separately.
  2. Get the SDK to use Target for Run/Debug by pointing Windows→Preference→Plug-in Development→Target Platform to the location of Target.
  3. Test Run/Debug.
  4. Add BeanShell plugins (org.beanshell) to Target platform. org.beanshell can be found from the download section for GenericFX at SourceForge.net.

Cinly’s preferred directory structure:

SDK./eclipse/sdk/eclipse_3.1.1
Target ./eclipse/targets/ide-dev for IDE Development (Used in normal development)
./eclipse/targets/ide for IDE
./eclipse/targets/rcp-dev for RCP Development
./eclipse/targets/rcp
for RCP

Note

AJDT 1.3 release on December 20, 2005 fails to work on my computer. Therefore, do not use AJDT version 1.3.0.20051220093604. I am using the AJDT 1.3RC, i.e., 1.3.0.20051214130641.

SDK setup

Install the versions with source and user documentations, a.k.a. SDK):

  1. eclipse-SDK-<version>-<os>.tar.gz
  2. GEF-SDK-<version>.zip
  3. AJDT (AspectJ Development)

Target setup

Do Application Specific Setup first. For RCP, you will need to look at RCP Setup section as well.

Setup Types

ideIDE setup for final packaging. No source code or documentation.
ide-devIDE setup for development.
rcpRCP setup for final packaging. No source code or documentation. See footnote for rcp-dev
rcp-devRCP setup for development. 1)

Application Specific Setup

For rcp:

  1. eclipse-RCP-<version>-<os>.tar.gz (”Runtime Binary”)
  2. eclipse-RCP-delta-pack.zip
  3. org.eclipse.ui.ide
  4. org.eclipse.core.filesystem (Eclipse 3.2)
  5. org.eclipse.core.runtime.compatibility
  6. org.eclipse.ui.views
  7. org.aspectj.weavingruntime - from AJEER (http://ajeer.sourceforge.net)
  8. org.eclipse.transformer - from AJEER

For ide:

  1. ecplise-platform-<version>-<os>.tar.gz (”Runtime Binary”)
  2. eclipse-JDT-<version>-<os>.tar.gz
  3. eclipse-PDE-<version>-<os>.tar.gz
  4. GEF-runtime-<version>.tar.gz
  5. org.aspectj.runtime_<version> from the AJDT SDK kit.
  6. org.aspectj.weavingruntime - from AJEER
  7. org.eclipse.transformer - from AJEER

For rcp-dev:

  1. eclipse-RCP-SDK-<version>-<os>.tar.gz (”Runtime Binary”)
  2. org.eclipse.ui.ide
  3. org.eclipse.core.runtime.compatibility
  4. org.eclipse.ui.views
  5. org.aspectj.weavingruntime - from AJEER
  6. org.eclipse.transformer - from AJEER

For ide-dev:

  1. ecplise-platform-SDK-<version>-<os>.tar.gz (”Runtime Binary”)
  2. eclipse-JDT-SDK-<version>-<os>.tar.gz
  3. eclipse-PDE-SDK-<version>-<os>.tar.gz
  4. GEF-SDK-<version>.tar.gz
  5. Full AspectJ, no need for AJDT.
  6. org.aspectj.weavingruntime - from AJEER
  7. org.eclipse.transformer - from AJEER

RCP Setup

It is necessary to add the following plugins:

Function required/used plugins to include
AspectJ org.aspectj.runtime
AJEER (http://ajeer.sourceforge.net) org.aspectj.runtime.weaveruntime (20080404: if not working, try org.eclipse.ajeer.runtime.weavingruntime instead)
org.eclipse.transformer
Help-related plugins org.apache.lucene
org.eclipse.help
org.eclipse.help.appserver
org.eclipse.help.base
org.eclipse.help.ui
org.eclipse.help.webapp
org.eclipse.tomcat
org.eclipse.ui.forms
Update-related plugins org.eclipse.ui.forms
org.eclipse.update.core
org.eclipse.update.scheduler
org.eclipse.update.ui
Console org.eclipse.text
org.eclipse.jface.text
org.eclipse.ui.console
org.eclipse.ui.workbench.texteditor
Intro pages org.eclipse.ui.intro

FIXME For some reasons, org.eclipse.resources may need to be copied separately into the RCP setup.

1) Some workspace plugins not used in RCP and tests plugins will fail to compile, but it is fine
 
developers/setup.txt · Last modified: 2008/04/04 17:27 by co224
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki