This guide explains how to get the Roller source code, build it with Maven, test it with Maven and run it via Maven, Jetty and Derby (recommended for development test purposes only). This build build applies to the current Roller trunk. Roller 5.1 requires JDK 1.7 or newer; Roller 5.0.x requires just JDK 1.6.
Eclipse users, you might wish to refer to this instead: Build and Run Roller 5 in Eclipse.
Get the Roller source code
There are two ways to get the source code, from the project's Git repository or from a source release. Here's how to get the Roller code directly from the Git repo:
git clone http://git-wip-us.apache.org/repos/asf/roller.git
Replace "http://" with "https://" in the above URLs if you are presently a Roller committer (i.e., have write access to Roller).:
If you are a GitHub user, you might find it easier to fork the Roller GitHub Repo: https://github.com/apache/roller.
Build Roller Weblogger
Here's how to build Roller Weblogger (also runs the unit tests).
cd roller mvn clean install
Run Roller Weblogger for development testing
Here's how to run the Jetty servlet engine, Derby and Roller for development testing of Roller:
cd roller/app mvn jetty:run
Build a Roller Weblogger release package
After running mvn clean install from from roller_trunk, navigate to its assembly-release subfolder and run mvn clean install again.
Check the Roller Install guide for instructions on deploying Roller to Tomcat and other web servers. Unlike mvn jetty:run above, these deployments will persist data to non-temporary databases so you don't have to start from scratch with each run.
The Roller team is also starting to use Selenium to automate in-browser testings (using just Firefox presently), mvn clean install from the Roller it-selenium folder will activate the Roller Selenium tests.
Check this page's child pages for development within IntelliJ IDEA and Eclipse, as well as how to do code tracing in IDEA while running Roller via mvn jetty:run.