Difference between revisions of "Corona/GettingStarted/Dev"

From Eclipsepedia

Jump to: navigation, search
(Step 3: Check-out Team Artifacts)
(Step 4: Download Target Platform Runtime)
Line 70: Line 70:
  
 
=== Step 4: Download Target Platform Runtime ===
 
=== 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.  
  
 
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 ''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.
Line 76: Line 76:
 
The following steps are performed within the ''Plug-in Development'' perspective.
 
The following steps are performed within the ''Plug-in Development'' perspective.
  
==== Step 4.1: Update Runtime Properties ====
+
==== Step 4.1: Proxy setup ====
 
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/target.platforms/runtime/build.xml'''
+
* Edit the Ant script '''team.corona/runtime/buildTargetRuntime.xml'''
* Find the Ant target ''init''
+
* Find the Ant target '''init '''
* Update (or comment out) the arguments for '''<setproxy .../>'''
+
* If needed, update (and comment out) the arguments for '''<setproxy .../>'''  
  
==== Step 4.2: Update Download URL ====
+
==== Step 4.2: Initialize ''target.platform'' Runtime ====
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. 
+
* ''Run'' the Ant script '''team.corona/runtime/buildTargetRuntime.xml'''
* 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''
 
* ''Refresh'' your workspace so it is aware of the files added to the ''target platform''
  

Revision as of 15:27, 23 July 2009

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 for RCP/Plug-in Developers installed, download and install the following:

Step 1.2: Install Subversive

The Eclipse Subversive plug-ins for SVN are not installed in the RCP/Plug-in distribution. However, they are provided via the Galileo update site. These plug-ins must be installed so that you can interact with Corona's SVN repository.

  • Select Help -> Install New Software...
  • Select the Available Software tab
  • In Work with field, select Galileo - http://download.eclipse.org/releases/galileo
  • Expand the Collaboration entry
  • Select the 2 SVN components to install
    • Subversion SVN Integration for the Mylyn Project
    • SVN Team Provider
  • Click Next
  • Click Next
  • Accept the License (Click Finish)
  • After the installation has been completed, Restart Eclipse

Step 1.3: Install Subversive Connectors

In order for Subversive plug-in to work, Subversive SVN Connector is necessary. They are provided by Polarion update site.

Step 2: Setup Subversion

Step 2.1: Setup the appropriate SVN Connector

  • Select Window -> Preferences
  • Expand Team
  • Select SVN
  • Select SVN Connector tab
  • In the SVN Connector field, select Native JavaHL
  • Click Ok

Step 2.2: Repository setup

  • Open the SVN Repository Exploring 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 team.corona 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: Proxy setup

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 team.corona/runtime/buildTargetRuntime.xml
  • Find the Ant target init
  • If needed, update (and comment out) the arguments for <setproxy .../>

Step 4.2: Initialize target.platform Runtime

  • Run the Ant script team.corona/runtime/buildTargetRuntime.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.platforms/eclipse-runtime.target
  • 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.