Page Comparison

...

• 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 on and deployment to the latest, in progress version of Sakai
• The '12.x' branch corresponds to the 12.x version family of the Sakai code base
• 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 versions 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 the leader. A new '12.x' maintenance branch will be cut from master, and master will effectively become what will later be known as version '13'', and as new versions of Sakai are cut and tagged, a matching version of the SCORM Player will be cut from the appropriate maintenance branch.

Building & Deploying the SCORM Player for Sakai 10+

...

Currently, if you rely on auto.ddl to create the SCORM tables during Tomcat startup, the hibernate mapping is incorrectly interpreted and creates some columns with the types LONG and LONG RAW. This is against the recommendation of Oracle (these datatypes have been deprecated), and the tool explodes if you try to use it. The issue has been raised and is being tracked @

In the mean time, you can use the following workaround to make the tool work with an Oracle database.

...