Jump to: navigation, search

Corona/GettingStarted/Dev

< Corona‎ | GettingStarted
Revision as of 09:24, 18 August 2008 by Dennis.oflynn.compuware.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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: Setup IDE Target Platform

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 .../>