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"
(New page: ==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 Eclips...) |
m (Steps 4 & 5) |
||
| Line 20: | Line 20: | ||
* Check-out ''corona.team'' folder | * Check-out ''corona.team'' folder | ||
| − | === Step 4: | + | === 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. | 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. | ||
| Line 33: | Line 33: | ||
* 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 .../>''' | ||
| + | |||
| + | ==== 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/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 | ||
[[Category: Corona]] | [[Category: Corona]] | ||
Revision as of 10:39, 18 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...
Step 1: Download Eclipse PDE/IDE
If you do not already have an Eclipse PDE/IDE installed, download and install the following:
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.
- 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
- 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/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/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