...

SCORM Player Installation Guide for Sakai 10+

Since the move to GitHub, the process for installing the SCORM Player in Sakai 10+ has been drastically simplified. You no longer need to worry about profiles, and the "wicket-for-scorm" project has been moved into the SCORM Player project as a sub-module. You simply need to select the correct version of the SCORM Player that corresponds to the version of Sakai you'll be deploying the tool to, get the source code, and build and deploy the tool like you would any other Sakai tool.

Versions in GitHub

You can find the SCORM Player source code in the SakaiContrib's GitHub account. From there, you can choose to either clone the repository to your local machine, or download a .ZIP file containing the source code. You'll notice that in the GitHub repository, there are several branches of the source code for you to choose from, each corresponding to a specific version, or version family, of Sakai:

• The 'master' branch corresponds with the 'master' branch of the main Sakai code base (commonly/previously referred to as 'trunk'), and should be used for development and deployment to the latest, in development version of Sakai
• The '11.x' branch corresponds to the 11.x version family of the Sakai code base
• The '10.x' branch corresponds to the 10.x version family of the Sakai code base

These '.x' branches are also commonly referred to as 'maintenance branches', and as new version of Sakai are cut and tagged, a matching version of the SCORM Player will be cut from the appropriate maintenance branch. For example, when the Community cuts and releases the official 11.0 tag from the main 11.x Sakai code base, the SCORM Player will follow suit and cut an 11.0 tag from it's own 11.x maintenance branch. The same can be said for releases in the 10.x version family.

When the time comes that the Community creates a 12.x branch, and ultimately releases a 12.0 release, the SCORM Player will naturally follow suit. A new '12.x' maintenance branch will be cut from master, and master will effectively become what will later be known as version '13'.

Building & Deploying the SCORM Player for Sakai 10+

Once you've selected the appropriate version of the SCORM Player for your instance of Sakai, and have downloaded the source code to your local machine in your preferred manner, building the source code should be very familiar. You simply issue the same Maven commands as you would for any other Sakai tool, from the directory where you've cloned or extracted the source:

$ cd /opt/src/git/scorm
$ mvn clean install sakai:deploy

That's all that's necessary to build and deploy the SCORM Player to your Sakai 10+ instance!

SCORM Player Installation Guide for Sakai 2.x

...