E-mailTroubleshooting Issues
Getting Help
Below are a number of common issues encountered while building and starting up Sakai but you may also benefit from the expert advice and assistance available within the Sakai developer community. The quickest way to get your questions answered is to join the Sakai Development Work Group (otherwise known as sakai-dev) and send an email to the list.
To join the sakai-dev list go to http://collab.sakaiproject.org, create a new account, log in to Collab, select the My Workspace tab, and then use the Membership tool to join the group named DG: Development. You can then begin to send emails to (and receive them from) sakai-dev@collab.sakaiproject.org. To later unsubscribe, you can simply use the same Membership tool to unjoin the site.
Build Issues
JAR download failures
A first build of Maven on a fresh installation may warn of numerous jar download failures if you include the clean phase. This is a nuisance, but not otherwise a problem. Even when doing a clean maven tries to download all dependencies, including those Sakai jars that may not be built until the later build phase. Once they are built and placed into the repository, maven is perfectly happy for the next "clean build" cycle. The upshot is that you may see these errors for your first build, but you shouldn't see them for subsequent builds. It also means that you're better off not including the clean phase during your first build of a new version of the code.
If this does not account for the download failures you're seeing, then you may want to double-check your maven.remote.repo setting. See the Maven Configuration section, and follow it precisely.
Out of Memory errors
You may find that your machine runs out of memory while it is building Sakai. As it turns out, maven does not read JAVA_OPTS when it starts up, and so if your build output complains of "Out of Memory" errors you'll need to set an additional environment variable, namely, MAVEN_OPTS. The value in the sample Unix command below should be more than enough:
export MAVEN_OPTS="-Xmx384m -XX:PermSize=48m"
Uninformative failure messages
If you need more detailed output to track down a build error, maven can be run in debug mode by adding the -x argument, e.g. mvn -x.