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 and, as of January 2010, the Roller trunk uses a Maven based build process. For information on building Roller 4.0 see BuildGuide40.
Get the Roller source code
There are two ways to get the source code, from the project's Subversion repository or from a source release. Here's how to get the code from Subversion:
svn co https://svn.apache.org/repos/asf/roller/trunk roller_trunk
TBD: how to get and extract a source release
Build Roller Weblogger
Here's how to build Roller Weblogger (also runs the unit tests).
cd roller_trunk mvn 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_trunk/weblogger-weba-- mvn jetty:run
Then use your web browser to browse to http://localhost:8080/roller to test Roller. You will find the log files in roller_trunk/weblogger-web/target/work. You can adjust logging levels via the Roller properties override file at roller_trunk/weblogger-web/src/test/resources/roller-custom.properties.
Build a Roller Weblogger release package
Building a Roller release package is a little more complex than just building and running Roller via the Maven Jetty plugin. Take a look at the three scripts in the root directory of Roller to see the steps required to build a release of Roller for Java EE, Tomcat or JBoss.
- build-javaee-release.sh
- build-tomcat-release.sh
- build-jboss-release.sh
Other resources
Here's an excellent blog post from Harald Wellmann that explains how to setup Eclipse and m2eclipse plugin to build, test and run Roller: http://hwellmann.blogspot.com/2010/02/setting-up-eclipse-for-roller.html