Jump to: navigation, search

Riena/Getting Started

{{#eclipseproject:rt.riena}}


For a Riena-based application to compile, a certain set of bundles (plug-ins) must be available at compile time. This set of bundles is known as target platform. Follow the steps below to set up the target platform for Riena applications.


Running the code samples and example client

1. Download Eclipse for RCP and RAP Developers and start with a blank workspace.


2. Download the RienaSetup project and import it into your workspace. Import project RienaSetup.png


3. In the imported project, open the file Riena_on_4x.target and set the target platform. Note: If you want to use Riena on an Eclipse 3.x or RAP basis, select the appropriate target definition. Target platform editor RienaSetup.png


4. Open the "Plug-Ins" view and import as source project:

  • org.eclipse.riena.example.client
  • org.eclipse.riena.sample.snippets (not relevant for Riena on RAP)

Import source project RienaSetup.png


5. In the project RienaSetup, select the launch configuration "SWT ExampleApplication E4" and add required plug-ins, then Run it. For Riena on Eclipse 3.x or RAP, use the appropriate launch configuration.

  • Explore the code and plugin.xml in the example project


5.1 For Riena on RAP comment the extension to org.eclipse.rap.ui.entrypoint on the bottom of the plugin.xml, ignore the displayed error.


6. Some specific techniques are demonstrated in the snippets project, imported in step 4.

Manual target platform setup

If you do not like to use the target definition files in the RienaSetup project like described in the above section, you can manually create a target platform description with Eclipse:

  • Create a new target platform definition under Window => Preferences => Target Platform => Add => Nothing: Start with an empty target platform => Next
  • Provide a name like "Riena Target Platform"
  • Click Add => Software Site
  • Select the p2 repository which contains the target components to install (see below)
  • Select the target components (see below)
  • Uncheck "Group by Category" otherwise you can't see all components
  • Uncheck "Include required software" if you are setting up Riena on RAP

The result should look like this: Riena Targetplatform RCP.png


The Riena components are contained in the Eclipse Kepler p2 repository. From there, you can also install the RCP and Equinox target components, which a Riena application needs to run.

Target components to install:

  • Riena Target Components for E4 or Riena Target Components for RAP
  • Riena Core Target Components for E4 and RAP
  • Riena Samples Target Components
  • Eclipse RCP
  • Eclipse RCP Plug-in Developer Resources
  • Eclipse RCP SDK
  • Equinox Target Components


Setting up Riena for Eclipse 3.8

Eclipse 3.8 is the last version of the Eclipse 3.x stream. Riena 5 comes with full support for Eclipse 3.8.

Riena for Eclipse 3.8 is in a separate p2 Repository - http://download.eclipse.org/rt/riena/5.0.0.0/e3.

RCP 3.8 and Equinox can be installed from http://download.eclipse.org/eclipse/updates/3.8.


Next Step

Now you are ready to start writing Riena applications. To get a feeling of the Riena framework, take a look at Riena's Example Applications and Code Templates.

Set up Riena Toolbox

For more details about the Riena Toolbox, look here http://wiki.eclipse.org/Riena/Toolbox.

Build your own Riena-Targetplatform

Riena provides a tycho-build to build a targetplatform from cvs head. Follows these steps:

Prerequisites:

Start the build:

  • Checkout the bundle org.eclipse.riena.build.tycho from cvs (:pserver:anonymous@dev.eclipse.org:/cvsroot/rt)
  • Open a shell and go to the directory org.eclipse.riena.build.tycho
  • Checkout the sources by executing: ant -f checkout.xml -DCHECKOUT_DIR=checkout -DTARGET_DIR=target
  • Go to target/org.eclipse.riena.build.tycho
  • Execute: mvn clean install -P all-modules -Dmaven.test.skip=true

At the moment Tycho can't handle the package import to javax.servlet, so we had to replace this with a dependencie. We accomplished this by patching the MANIFEST.MF from the bundle org.eclipse.communication.core after the checkout. There may be other issues with the result of this build or the buildprocess itself, so be aware that this is not yet production ready.