Page History

...

   cd roller_trunk 
   mvn clean install 

Run Roller Weblogger for development testing

...

   cd roller_trunk/weblogger-webappapp
   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-webapp/target/work. You can adjust logging levels via the Roller properties override file at roller_trunk/weblogger-webapp/src/test/resources/roller-customjettyrun.properties. Note the blog information stored during each mvn jetty:run session will be lost once you stop Jetty (i.e., each mvn jetty:run starts with empty Roller database tables).

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

After running mvn clean install from from roller_trunk, navigate to its assembly-release subfolder and run mvn clean install again.

Other resources

Check the http://svn.apache.org/viewvc/roller/trunk/docs/ for deployment information on Tomcat, GlassFish, or JBoss. 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.

For Roller 5.0.1 and earlier, hereHere'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