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 "Corona/GettingStarted/Dev"
(→Step 2: Setup Subversion) |
|||
| Line 59: | Line 59: | ||
It is common for Corona developers to work behind a firewall. For Corona to be able to properly setup its ''target platform'', it needs to be able to download plug-ins from external repositories. | It is common for Corona developers to work behind a firewall. For Corona to be able to properly setup its ''target platform'', it needs to be able to download plug-ins from external repositories. | ||
| − | * Edit the Ant script '''corona.team/runtime/build.xml''' | + | * Edit the Ant script '''corona.team/target.platforms/runtime/build.xml''' |
* Find the Ant target ''init'' | * Find the Ant target ''init'' | ||
* Update (or comment out) the arguments for '''<setproxy .../>''' | * Update (or comment out) the arguments for '''<setproxy .../>''' | ||
| Line 65: | Line 65: | ||
==== Step 4.2: Update Download URL ==== | ==== Step 4.2: Update Download URL ==== | ||
Eclipse resources are available from many download mirrors. You will need to figure out which one is best to use to update your ''target platform'' environment. | Eclipse resources are available from many download mirrors. You will need to figure out which one is best to use to update your ''target platform'' environment. | ||
| − | * Edit the Ant script '''corona.team/runtime/build.properties''' | + | * Edit the Ant script '''corona.team/target.platforms/runtime/build.properties''' |
* Update the value for ''eclipse.download.mirror'' | * Update the value for ''eclipse.download.mirror'' | ||
Revision as of 08:14, 19 August 2008
Contents
Setting Up Corona Development Environment
Corona's development environment is based upon the Eclipse PDE/IDE. All of Corona's server-side components are either OSGi Bundles or Eclipse Plug-ins.
- Note
- It is assumed the you are familiar with Eclipse IDE, Subversion, etc...
- The following steps should be performed in a new workspace
Step 1: Setup Eclipse PDE/IDE
Step 1.1: Download IDE
If you do not already have an Eclipse PDE/IDE installed, download and install the following:
Step 1.2: Install Subversive
The Eclipse Subversive plug-ins for SVN are not installed in the RCP/IDE distribution. However, they are provided via the Ganymede update site. These plug-ins must be installed so that you can interact with Corona's SVN repository.
- Select Help -> Software Updates...
- Select the Available Software tab
- Expand the Ganymede entry
- Expand the Collaboration Tools entry
- Select the 3 SVN components to install
- Subversion Integration for Mylyn
- SVN Team Provider
- SVN Team Provider Localization
- Select the Install button
Step 1.3: Install Subversive Connectors
Please follow the instructions for installing the Eclipse Subversive plug-ins that are available on the Eclipse Subversive's download page.
Step 2: Setup Subversion
Corona's source repository is managed by Subversion. You will need to install the Eclipse Subversive plug-ins and define a repository location for Corona.
- Switch to the SVN Repository perspective
- Select File -> New -> Repository Location
- Complete the New Repository Location dialog
- Committer Repository URL
- svn+ssh://dev.eclipse.org/svnroot/technology/org.eclipse.corona
- Contributor Repository URL
- http://dev.eclipse.org/svnroot/technology/org.eclipse.corona
Step 3: Check-out Team Artifacts
Corona provides team artifacts to help team member participate in the community. Some of these artifacts are used to setup the workspace used for Corona development
- Switch to the SVN Repository perspective
- Expand the entry for Corona's SVN repository
- Expand the entry for trunk
- Check-out corona.team folder
Step 4: Download Target Platform Runtime
Corona uses the target platform capability of the IDE. This allows the IDE to simulate the platform where the plug-ins under development will eventually be deployed.
The target platform is default set of Equinox, Eclipse Core, and 3rd party libraries used in a server-side environment. This environment is setup using an Ant script within the team's artifacts.
The following steps are performed within the Plug-in Development perspective.
Step 4.1: Update Runtime Properties
It is common for Corona developers to work behind a firewall. For Corona to be able to properly setup its target platform, it needs to be able to download plug-ins from external repositories.
- Edit the Ant script corona.team/target.platforms/runtime/build.xml
- Find the Ant target init
- Update (or comment out) the arguments for <setproxy .../>
Step 4.2: Update Download URL
Eclipse resources are available from many download mirrors. You will need to figure out which one is best to use to update your target platform environment.
- Edit the Ant script corona.team/target.platforms/runtime/build.properties
- Update the value for eclipse.download.mirror
Step 4.3: Initialize target.platform Runtime
- Run the Ant script corona.team/runtime/build.xml
- Refresh your workspace so it is aware of the files added to the target platform
Step 5: Define Workspace Target Platform
Each Plug-in Development Workspace can be configured for a specific target platform.
- Select the Windows -> Preferences menu item
- Expand the Plug-in Development entry
- Select Target Platform
- Select the Browse button
- Navigate the corona.team tree and select corona.team/target.platform
- Select the Load Target button
- Select the Ok button
Step 6: Check-out Corona Sources
- Switch to the Plug-in Development perspective
- Within the Package Explorer view, expand the corona.team entry
- Expand the project.sets folder
- Right-mouse-click corona-all.psf
- Select import
- Select Team -> Team Project Set
- Select Finish
- Note
- Corona's team project set also defines working sets to help organize Corona's plug-ins within your development workspace.