Building OpenRemote 2.0 Developer Releases

OpenRemote 2.0 is hosted on a Subversion repository. Familiarity with Subversion is assumed. Subversion source checkouts are otherwise self-sufficient. Database dependencies (MySQL) exist for online components (Designer and Beehive database).

Java 6 or later is required

Subversion Checkout

Stable developer releases of the OpenRemote 2.0 platform are tagged in Subversion under /tags directory. Developer releases use Alpha suffix. A full OpenRemote 2.0 checkout will include all platform components (iPhone, iPad, Android, Web consoles, Controller, Online Designer and Beehive Database).

Therefore, under /tags/OpenRemote_Boss_2_0_0_Alpha8 for example, you will find the following components:

You can checkout components individually (only Controller or Android components, for example) to save bandwidth and make the checkout operation faster.

To checkout the entire platform release, use:

  svn co http://openremote.svn.sourceforge.net/svnroot/openremote/tags/OpenRemote_Boss_2_0_0_Alpha8

Example above uses Alpha8 but check the content of /tags directory of the latest stable developer release tag.

To checkout a specific component (OpenRemote Controller in this case), use:

  svn co http://openremote.svn.sourceforge.net/svnroot/openremote/tags/OpenRemote_Boss_2_0_0_Alpha8/Controller_2_0_0_Alpha11

Platform Components

A full OpenRemote 2.0 checkout will include 'Tools' and 'Runtime' components. These are used to ensure the builds are self-sufficient. Under the 'Tools' directory you will find a version of Apache Ant that can be used to build the source checkout. The build.xml scripts have been tested against this version of Ant.

Under 'Runtime' directory you will find a Apache Tomcat runtime that has been configured for OpenRemote 2.0 Controller deployment. You can use this Tomcat configuration for deploying your built controller.war file.

Other directories are named after their corresponding OpenRemote components.

Building OpenRemote 2.0 Controller

Under the Controller_2_0_0 directory you will find an Ant build.xml file. You can build the Controller web archive with following:

>  cd Controller_2_0_[x_suffix]
> ../Tools/apache-ant-1.7.0/bin/ant war
Buildfile: build.xml

clean:


 ...


war:
     [echo] --------------------------------------------------------------------
     [echo]  Packing war...
     [echo] --------------------------------------------------------------------
     [echo]
      [war] Building war: /Users/juha/openremote/tags/OpenRemote_Boss_2_0_0_Alpha8/
            Controller_2_0_0_Alpha11/output/controller.war

BUILD SUCCESSFUL
Total time: 15 seconds

The 'war' target in Controller's build.xml will create a web archive under 'output' directory.

To run unit test suite on the Controller, execute

> ../Tools/apache-ant-1.7.0/bin/ant run-test


...

    [junit] Tests run: 168, Failures: 3, Errors: 2, Time elapsed: 22.325 sec
    [junit] Test org.openremote.controller.suite.AllTests FAILED
[junitreport] Processing /Users/juha/openremote/tags/OpenRemote_Boss_2_0_0_Alpha8/
              Controller_2_0_0_Alpha11/build/junit_report/TESTS-TestSuites.xml

You will find the jUnit report under the '/build/junit_report' directory.

Deploying OpenRemote 2.0 Controller

You can deploy your built Controller into 'Runtime' directory.

First, unpack the web archive located in the Controller's 'output' directory:

> cd output
> jar xf controller.war
> rm controller.war
> cp -r * ../../Runtime/apache-tomcat-6.0.18/webapps/controller/

Switch to /bin and start the controller:

> cd ../../Runtime/apache-tomcat-6.0.18/bin
> sh openremote.sh run

...

Aug 25, 2010 11:53:39 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 4053 ms

You will now find the controller at http://localhost:8080/controller

See Also

• Building OpenRemote iPhone 2.0 Console
• Building OpenRemote Android 2.0 Console