You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Ode is still under incubation and doesn't have any official release yet (but we're working on it). So you will have to build from the source code but thanks to Buildr, this is fairly easy.

We're still maintaining a Maven2 build for now but the preferred build mechanism is using Buildr as our Maven2 support will shortly been discontinued.

Getting the source code

First you will have to make sure that you have Subversion. If you don't know what Subversion is or don't have it installed, check here. Once installed run:

$> svn checkout http://svn.apache.org/repos/asf/incubator/ode/trunk ode

For more information or if you have any problem with Subversion (like being behind a proxy or a firewall) check the Source Code section.

Building With Buildr

If you already have Ruby installed on your machine (which is true for most Linux and Mac computers), you will probably find building with Buildr easier. You will need to following things:

  • Ruby 1.8.x with RubyGems 0.9 or later. As mentioned, you probably already have this installed. For Windows users using the Ruby One-Click Installer is the easiest (http://rubyforge.org/projects/rubyinstaller/). For Linux or Mac OS users, a Ruby interpreter is usually preinstalled. Just make sure to have the ruby-dev package (mkmf is needed for RJB).
  • Buildr. Install it by running 'gem install buildr 1.1.3'. You will need to have a proper JAVA_HOME environment variable. Make sure to choose either win32 or ruby platforms (don't choose java for Antwrap, that's JRuby).

Building is then pretty simple. Open a command in the source root directory and run:

rake TEST=no package

To try the test cases bundled with ODE:

rake test

To generate Eclipse project files:

rake eclipse

It just works! For more information about Buildr see http://buildr.rubyforge.org/.

Troubleshooting

  • At the moment the ODE build only supports buildr 1.1.3 so make sure that you have this version installed.
  • If you get a Zlib:BufError, that's because of your version of Rubygems, just upgrade RubyGems by typing: 
    gem update --system
  • No labels