[Building Sakai] Scorm player for sakai 2.6

[Anthony Whyte]

Looking over the various SCORM projects in contrib plus the one  
available from EDIA (there is also the Icodeon player) presents  
something of a confusing picture for deployers.  Only one of the  
contributions (EDIA) makes tags available (2.5.3 is the latest) while  
the Sakai dependency declarations in all the various projects' trunk  
code are out-of-date (e.g., 2.6.0RC1-SNAPSHOT, entitybroker 1.2.0).

I recognize that contrib projects vary in quality and range from R&D  
efforts to mature projects.  Caveat emptor is the doctrine that rules  
for deployers choosing contrib code but we do ourselves no favors as a  
Community by letting capabilities such as SCORM integration fall  
behind the pace of our 2.x (and looking to the horizon, 3.x)  
development.  Forcing deployers--many with little Maven experience--to  
seek out patches or hand craft pom files in order to make SCORM work  
in Sakai does nothing to reduce the barriers to entry for which we are  
often justly criticized.

I assume the EDIA runtime player is the project of choice at the  
moment.  I recommend that the UCT 2.6.x patch (itself now a bit out-of- 
date) be applied to EDIA trunk.  Then update the base pom <parent>  
together with any other moldy Sakai dependencies such as entitybroker  
1.2.0 (update it to 1.3.6 at a minimum) as well as check the poms for  
any other issues.  Then branch trunk for 2.6.x and tag it.  After that  
update trunk to work with 2.7.0, branch it and tag a beta candidate.   
Perhaps all the EDIA scorm code could be contributed back to the  
community and located in Contrib under /scorm or /edia.  There are  
other things we could do to simplify the release process like  
implement the Maven release plugin but at a minimum I encourage the  
developers maintaining this code to update it and make available  
usable tags.

I can help out with this work.

Anthony


http://confluence.sakaiproject.org/display/SCORMPLAYER/SCORM
http://confluence.sakaiproject.org/display/SCORMPLAYER/SCORM+in+Sakai


EDIA (based on SCORM.2004.3ED.RTE)

https://svn.edia.nl/edia-sakai/edia-sakai-scorm/

branches: 2.5.3
tags: 2.5.2, 2.5.3
trunk: <parent> = 2.5.3; entitybroker dependency=1.2.0; <scm>  
incorrectly points to contrib SCORM.2004.3ED.RTE
UCT 2.6.x patch = http://source.cet.uct.ac.za/svn/sakai/patches/trunk/edia_scorm_player_poms.diff 
   (<parent> = 2.6.0RC1-SNAPSHOT)

SCORM.2004.3ED.RTE
trunk: <parent> = 2.6.0RC1-SNAPSHOT; entitybroker dependency=1.2.0
branches:  2.4.x, 2.5.x only
tags: none

scorm-hkust
trunk: compatible with Sakai 2.4; Confluence page above says it's  
ported to 2.5.3 but trunk is not set up for Maven2
branches: none
tags: none

ibmtracker4learning
trunk: unsure which version of Sakai this is targeted at
branches: none
tags: none

runtimetool  (deprecated I believe)
trunk: not setup for Maven2
branches: 2.1, 2.2
tags: none



On Jan 7, 2010, at 8:24 AM, David Horwitz wrote:

> Hi Given,
>
> We have a patch to update the poms of the edia scorm player to build  
> against sakai 2.6:
>
> http://source.cet.uct.ac.za/svn/sakai/patches/trunk/edia_scorm_player_poms.diff
>
> That should update the poms as necessary...
>
> D
>
> On 01/07/2010 03:05 PM, Steve Swinsburg wrote:
>>
>> Hi Given,
>>
>> You need to edit the poms for the Scorm player project, not master.  
>> When you check out the source, there will be one in the root of the  
>> checkout, then one in each module (directory) under the root. Find  
>> them and edit them all, although some may not have these  
>> dependencies, which is normal.
>>
>> cheers,
>> Steve
>>
>>
>>
>> On 07/01/2010, at 11:53 PM, given.shirinda at sita.co.za wrote:
>>
>>
>>> Hi Steve and other sakai team.
>>>
>>> I am still struggling getting scorm player running on sakai 2.6.
>>>
>>>
>>> as you said last time,I should just remove all org.sakaiproject  
>>> dependencies and replace them with the
>>> three:
>>>  <dependency>
>>> <groupId>org.sakaiproject.kernel</groupId>
>>> <artifactId>sakai-kernel-api</artifactId>
>>> </dependency>
>>>  <dependency>
>>> <groupId>org.sakaiproject.kernel</groupId>
>>>  <artifactId>sakai-component-manager</artifactId>
>>>  </dependency>
>>>  <dependency>
>>>  <groupId>org.sakaiproject.kernel</groupId>
>>>  <artifactId>sakai-kernel-util</artifactId>
>>>  </dependency>
>>>
>>> which pom.xml to edit,it's for scorm or master in sakai project.
>>>
>>> Also send me the sample pom.xml that's editted.
>>>
>>> Best Regards
>>>
>>> Given
>>>
>>>
>>> -- 
>>> E-learning Specialist
>>> SAKAI
>>> ________________________________________________
>>> Tel :012 470 1526
>>> Cell:0730133879
>>> @:given.shirinda at sita.co.za
>>> Alt@:given.shirinda at gmail.com
>>> ________________________________________________
>>> A person who moves too quickly may go wrong way.
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>>  with a subject of "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100107/7205cd41/attachment.html