Chariot Training Classes

Training Courses

I run Chariot's training and mentoring services. We provide training in AngularJS, HTML5, Spring, Hibernate, Maven, Scala, and more.

Chariot Education Services


Chariot Emerging Tech

Learn about upcoming technologies and trends from my colleagues at Chariot Solutions.


Chariot Conferences


« Roo (in the) Corner - new features in trunk... | Main | Webflow on Grails and jQuery UI with Grails at the Philly on Grails User Group Meeting »

Living on the Edge of a Roo - working on the trunk

Let's say you're an add-on developer or someone who wants to stay current with the refactorings of Roo 1.2. Since it is in active development, you need to do two things to make your project work with the latest code. Remember, this is bleeding edge, so don't be surprised if your Maven gets ahead of your snapshot builds...

Install the CI build

First, download the most recent build from the CI server at Install it as roo in your symlinks (unix/OS X) or add to the path for Windows.

On my OS X system, I call it rooss, and I keep M1 as roo.

Set up your snapshot repo and Roo version

Next, edit your pom.xml file and change the roo.version to 1.2.0.BUILD-SNAPSHOT - the punctuation is very important to Maven here. You'll need to add the Roo snapshots repository to your repository list:

    <name>Spring Roo Repository</name>

Then, you can do a mvn package and you should be on your way.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments (2)

You can also download and build the current trunk from source. Now from github:

It's very easy, just follow the readme.txt instructions.

Actually it's a simple mvn clean install (with maven 3 and Java 6 and a MAVEN_OPTS for mempry), but you need to configure gpg before (very easy in Mac, not to difficult in windows and not too bad in Ubuntu) But you tell us in a previous POST how to avoid the signature step ;)

Then a ln -s in *NIX:
sudo ln -s $ROO_HOME/bootstrap/roo-dev /usr/bin/roo-dev
sudo chmod +x /usr/bin/roo-dev

In windows, add roo-dev to the path.

You can even debug Roo importing the projects in Eclipse. Existing in workspace if you previously run mvn install eclipse:clean eclipse:eclipse

October 18, 2011 | Unregistered Commenterjbbarquero (Javier)

Excellent point. I had troubles early on with remembering to set up my GPG key and every time I got around to it, it was too late. This is a little less work, and it acts like the final product as opposed to running it from the project directory. However, I agree, that's probably the best way to make 100% sure you have the right 'stuff' in your build.


October 18, 2011 | Registered CommenterKen Rimple

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>