Child pages
  • Creating a Development Environment for Scheduling Assistant
Skip to end of metadata
Go to start of metadata


This document is intended to help deployers setup a development environment for modifying the Scheduling Assistant. This is not technically required if you don't plan to make any changes; see the overlay documentation on how to quickly deploy an instance of the application with minimal changes.


The Scheduling Assistant is a multi-module Maven Java project. It's deliverables include a Web Application that is deployed in Apache Tomcat and a JSR-168 Portlet.

Before you begin, you will first need to create an account on Github. Once you've got an account, follow their instructions to Set up git. After your workstation is setup, learn how to fork a repository.

Create your fork from

Now that you've got a fork, you'll need to use the address to your fork when "Cloning the repository" in Eclipse. The address will be viewable at something like

4 minute video demonstrating how to check out the source in Eclipse to get started developing:


If you have new features you'd like to contribute back to the project, our move to git has made it very easy:

  1. Make sure your work is done on a branch - not on master!
  2. Follow the steps in the uPortal Git Workflow document: Git Workflow for Non-Committers
  3. Send a Pull request when done!

Quick start with Bedework

  1. Download Apache Tomcat 6, unpack. Edit server.xml to expose the HTTP connector on port 9080 (so as not to conflict with a Bedework Quickstart instance you may also have running locally on 8080).
  2. Check out the Scheduling Assistant source per the video.
  3. In the root of the project, copy as and edit the tomcat.home property to match the root of your Tomcat 6 install.
  4. Navigate to sched-assist-war/src/main/resources, copy as Edit the properties to match your Bedework environment.
  5. In the root of the project, execute 'mvn package' to build the project. Since you are using Tomcat 6, you can activate the tomcat6 profile and get pre-compiled JSPs (run 'mvn package -P tomcat6')
  6. Open another terminal window, navigate to the Scheduling Assistant source root. Execute 'ant hsql' to start up an HSQLDB instance
  7. In the original terminal window, execute 'ant hsql-initialize-firstrun' to create the tables and sequences in the HSQLDB instance.
  8. Execute 'ant redeploy-war' to deploy the Scheduling Assistant war to your Tomcat install.
  9. Start Tomcat, and visit http://localhost:9080/scheduling-assistant/
  • No labels