Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "IAM Target Platform"
(→Install the required bundles) |
|||
| Line 16: | Line 16: | ||
== Install the required bundles == | == Install the required bundles == | ||
| − | The [ | + | The [http://dev.eclipse.org/svnroot/technology/org.eclipse.iam/trunk/dev-tools/iam-prep-target-platform.xml iam-prep-target-platform.xml (ANT Script)] uses [http://ant.apache.org/ Ant 1.6.5+] & the [http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html P2.director application] to populate the target-platform with the selection of plugins and features that IAM uses to build & test against. |
| − | + | The iam-prep-target-platform.xml ant script is checked into subversion at [http://dev.eclipse.org/svnroot/technology/org.eclipse.iam/trunk/dev-tools/], you should check out all of trunk anyway if you are going to be working on IAM. | |
| − | * Most bundles come from ganymede update site. '''TODO:''' specify versions to avoid changes | + | Basic operation of ant script... |
| − | * AJDT is downloaded from | + | {{codeblock|[dev-tools]$ ant -f iam-prep-target-platform.xml}} |
| − | * Some bundles are downloaded from | + | |
| − | * JTidy is downloaded from [http://q4e.googlecode.com q4e] | + | The ant script expects an Eclipse SDK installation to be present in the trunk/dev-tools/eclipse folder. |
| + | |||
| + | * Most bundles come from [http://download.eclipse.org/releases/ganymede/ ganymede update site]. | ||
| + | ** ('''TODO:''' specify versions to avoid changes with maintenance releases.) | ||
| + | * AJDT is downloaded from the [http://download.eclipse.org/tools/ajdt/34/update/ AJDT update site]. | ||
| + | * Some bundles are downloaded from [http://download.eclipse.org/tools/orbit/downloads/drops/R20080807152315/ Orbit]. | ||
| + | * JTidy is downloaded from [http://q4e.googlecode.com q4e]. | ||
| + | ** ('''TODO:''' a CQ for JTidy it is warranted, but maybe not needed if we upgrade the embedder) | ||
== Configure a target definition == | == Configure a target definition == | ||
Revision as of 18:03, 5 December 2008
< To: IAM Environment
Contents
Setting up the Target Platform
This page describes the process for setting up the target platform used to build IAM.
Create the base folder
Create a target-platform folder somewhere in your filesystem.
Install a new eclipse SDK
- Download the SDK from:
- Install on your target-platform folder
You should get the eclipse folder inside your target-platform folder.
Install the required bundles
The iam-prep-target-platform.xml (ANT Script) uses Ant 1.6.5+ & the P2.director application to populate the target-platform with the selection of plugins and features that IAM uses to build & test against.
The iam-prep-target-platform.xml ant script is checked into subversion at [1], you should check out all of trunk anyway if you are going to be working on IAM.
Basic operation of ant script...
[dev-tools]$ ant -f iam-prep-target-platform.xml |
The ant script expects an Eclipse SDK installation to be present in the trunk/dev-tools/eclipse folder.
- Most bundles come from ganymede update site.
- (TODO: specify versions to avoid changes with maintenance releases.)
- AJDT is downloaded from the AJDT update site.
- Some bundles are downloaded from Orbit.
- JTidy is downloaded from q4e.
- (TODO: a CQ for JTidy it is warranted, but maybe not needed if we upgrade the embedder)
Configure a target definition
Target platforms are managed through target definition files. You will need to set up your own target definitions.
- Start your eclipse (i.e. do not use the new installation you've just set up)
- Create a new (simple) project. You can name it Target Platform
- File > New > Other... > Plug-in Development > Target Definiton
- Enter iam-ganymede as the name of the file
- Set Target Name to IAM Ganymede
- Set Target Location to your target-platform/eclipse folder.
- Click on Set as Target Platform (you will need to repeat this last step if you change the bundles installed on your target definition).