[Building Sakai] Sharing Resources across courses in 2.8.0
Jim Mezzanotte
jmezzanotte at rsmart.com
Thu Mar 14 06:26:17 PDT 2013
An alternative to making files public is to add the ".auth" role to a
site. Files are still available to any user logged into Sakai, but
they're not public--you can make files available only to site members.
This approach probably works best if you're using a single site as a
central content repository, because you'll need to add the .auth role
via the Realms tool in the admin WS. The easiest method is to create
the .auth role by copying an existing role. Then, strip out all
permissions except for the "content.read" permission.
Best,
Jim Mezzanotte
On Wed, Mar 13, 2013 at 3:00 PM,
<sakai-dev-request at collab.sakaiproject.org> wrote:
> Send sakai-dev mailing list submissions to
> sakai-dev at collab.sakaiproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> or, via email, send a message with subject or body 'help' to
> sakai-dev-request at collab.sakaiproject.org
>
> You can reach the person managing the list at
> sakai-dev-owner at collab.sakaiproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sakai-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Moving tomcat/components folder (Aaron Zeckoski)
> 2. Re: Restoring deleted resources (Christian Aziz)
> 3. Re: Moving tomcat/components folder (Robert Sedzik)
> 4. ADD new templates to FCKeditor (SamuelGJ)
> 5. Re: Sakai 2.9.1 and tomcat 7 (SamuelGJ)
> 6. Re: Deploying Sakai 2.9.1 on Linux , tomcat7 and Oracle10g
> (Steve Swinsburg)
> 7. Re: CKEditor & Spelling correction. (Steve Swinsburg)
> 8. Re: Moving tomcat/components folder (Steve Swinsburg)
> 9. Re: CKEditor & Spelling correction. (Kevin Takacs)
> 10. Re: CKEditor & Spelling correction. (Gregory Guthrie)
> 11. Re: CKEditor & Spelling correction. (Steve Swinsburg)
> 12. Re: CKEditor & Spelling correction. (John Bush)
> 13. Reg : Sakai 2.9.2 google docs inetgration (prabhu)
> 14. Returning JSON from createEntity (Adrian Fish)
> 15. Sharing Resources across courses in 2.8.0 (David Wafula)
> 16. Re: Returning JSON from createEntity (Nguni Phakela)
> 17. Re: Sharing Resources across courses in 2.8.0 (Adam Marshall)
> 18. Re: Sharing Resources across courses in 2.8.0 (David Wafula)
> 19. Re: Sharing Resources across courses in 2.8.0 (Adam Marshall)
> 20. sharing Resources on SAKAI , , , and images in Question Pool
> (Fatima Rahiman)
> 21. Re: sharing Resources on SAKAI , , , and images in Question
> Pool (Robert Sedzik)
> 22. Re: Sharing Resources across courses in 2.8.0 (Steve Swinsburg)
> 23. Re: Returning JSON from createEntity (Adrian Fish)
> 24. Re: Returning JSON from createEntity (Aaron Zeckoski)
> 25. Re: Returning JSON from createEntity (Adrian Fish)
> 26. Re: Returning JSON from createEntity (Aaron Zeckoski)
> 27. Re: Sakai 2.9.1 and tomcat 7 (Fatemeh Asl)
> 28. Re: Spring 3.2 and Hibernate 3.6 upgrades (KNL-515 / KNL-517)
> (Earle Nietzel)
> 29. Re: CKEditor & Spelling correction. (Gregory Guthrie)
> 30. CLE Team Call, Thursday, 2013-03-14, 10:00EST (15:00GMT)
> (ottenhoff at longsight.com)
> 31. Re: CKEditor & Spelling correction. (Kevin Takacs)
> 32. mvn repository on source.sakaiproject.org are not availabale
> (Fatemeh Asl)
> 33. Samigo Question (Omer A Piperdi)
> 34. Re: CKEditor & Spelling correction. (Gregory Guthrie)
> 35. Samigo time assesment issue in Sakai 2.9 (Kaufmann,Melody-Ann J)
> 36. Re: Sakai 2.9.1 and tomcat 7 (SamuelGJ)
> 37. Re: Sakai 2.9.1 and tomcat 7 (David Horwitz)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 12 Mar 2013 15:01:32 -0400
> From: Aaron Zeckoski <azeckoski at unicon.net>
> Subject: Re: [Building Sakai] Moving tomcat/components folder
> To: Robert Sedzik <robert.sedzik at uadm.uu.se>
> Cc: sakai-dev at collab.sakaiproject.org
> Message-ID:
> <CAMTQKL=u=TJR79jFgZU-Bz678hDDoWSB3ORpwc4HDmouoZ8chg at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I think that providing a property like
> -Dsakai.components.root=/path/to/components on your java (tomcat) OPTS
> will allow you to override the default value.
>
> See loadComponents() in
> kernel/component-manager/src/main/java/org/sakaiproject/component/impl/SpringCompMgr.java
>
> I haven't tried this myself but it looks like it should work based on the code.
> Worst case scenario, just change the default in that method.
>
> NOTE: this is a runtime change only, the build will not be affected by this
> -AZ
>
>
>
> On Tue, Mar 12, 2013 at 2:41 PM, Robert Sedzik <robert.sedzik at uadm.uu.se> wrote:
>> Hi all,
>>
>> It is possible to move the tomcat/components folder to another location
>> and start sakai
>> via a jvm/tomcat switch or by other means to set an alternate
>> tomcat/components path?
>>
>> I have not been able to find a sakai property (sakai.properties)
>> so I have been trying to do it via code. Changing in sakai kernel with
>> no success so far.
>> I am assuming because of tomcat/lib dependencies (spring).
>>
>> Cheers,
>> Robert
>>
>>
>>
>> _______________________________________________
>> 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"
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 12 Mar 2013 15:15:32 -0400
> From: Christian Aziz <caziz at rutgers.edu>
> Subject: Re: [Building Sakai] Restoring deleted resources
> To: Adam Marshall <adam.marshall at it.ox.ac.uk>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAJ5T9PaqU5pDU8mzpLc3MwNfBj5eUFEERCy+2OiecHGowmam0Q at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> I'd vote to reopen this issue. What we currently do is backup our files
> nightly and produce a list of pointers to them on our NetApp. When users
> call us to restore deleted items, we have to go through the arduous process
> of finding the pointer to each deleted file in the list, searching and
> downloading it from the NetApp snapshot, then reuploading it.
>
>
>
> Christian V. Aziz
> Project Manager - OIRT
> Coadjutant Faculty - SC&I
> Rutgers, The State University of New Jersey
>
> 101I Administrative Services Building Annex 1
> 56 Bevier Road, Piscataway, NJ 08854
> Tel: 848-445-8732 | Fax: 732-445-5539
>
>
> On Tue, Mar 12, 2013 at 6:32 AM, Adam Marshall <adam.marshall at it.ox.ac.uk>wrote:
>
>> Are you saying this patch doesn?t work for users? We run it in
>> production and have no problems.****
>>
>> ** **
>>
>> One thing I?d like to ask is why o why it isn?t part of the core sakai
>> distribution? I fail to see how an institution can live without a recycle
>> bin.****
>>
>> ** **
>>
>> What needs to be done to get it into 2.10? ****
>>
>> ** **
>>
>> I see the issue has been closed with a wont fix. Should I reopen it?****
>>
>> ** **
>>
>> Adam****
>>
>> ** **
>>
>> *From:* sakai-dev-bounces at collab.sakaiproject.org [mailto:
>> sakai-dev-bounces at collab.sakaiproject.org] *On Behalf Of *Paul Dagnall
>> *Sent:* 11 March 2013 21:36
>> *To:* sakai-dev
>> *Subject:* [Building Sakai] Restoring deleted resources****
>>
>> ** **
>>
>> I'm testing restoring deleted (Resources) files in Sakai 2.6 because we've
>> migrated our binary content out of the database and onto a file server.
>> Long story on why we waited so long to do this...
>>
>> I delete the file. I look at the CONTENT_RESOURCE_DELETE table, and
>> scratch my head because it's useless for finding where the file used to be.
>> So do we have to restore the CONTENT_RESOURCE database records to get the
>> correct path before we can get the file from a backup?
>>
>> Am I overlooking something?
>>
>> I see SAK-1525 <https://jira.sakaiproject.org/browse/SAK-1525> but much
>> of it looks up in the air.
>>
>> The good news is we are soon going to roll out 2.9 and the
>> CONTENT_RESOURCE_DELETE table has sufficient info to get the file back.
>>
>> Thanks!
>>
>> ****
>>
>> Paul Dagnall
>> Application Developer & Administrator
>> University of Dayton****
>>
>> ** **
>>
>> _______________________________________________
>> 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/20130312/42bffa7b/attachment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Tue, 12 Mar 2013 20:27:12 +0100
> From: Robert Sedzik <robert.sedzik at uadm.uu.se>
> Subject: Re: [Building Sakai] Moving tomcat/components folder
> To: Aaron Zeckoski <azeckoski at unicon.net>
> Cc: sakai-dev at collab.sakaiproject.org
> Message-ID: <513F8190.60004 at uadm.uu.se>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thanks, I missed that -Dsakai.components.root thing.
>
> kernel/component-manager/src/main/java/org/sakaiproject/component/impl/SpringCompMgr.java
>
>
> is actually kernel part I am hacking.
>
> Thanks for the fast reply.
>
> Rob
>
>
>
> On 12-Mar-13 8:01 PM, Aaron Zeckoski wrote:
>> I think that providing a property like
>> -Dsakai.components.root=/path/to/components on your java (tomcat) OPTS
>> will allow you to override the default value.
>>
>> See loadComponents() in
>> kernel/component-manager/src/main/java/org/sakaiproject/component/impl/SpringCompMgr.java
>>
>> I haven't tried this myself but it looks like it should work based on the code.
>> Worst case scenario, just change the default in that method.
>>
>> NOTE: this is a runtime change only, the build will not be affected by this
>> -AZ
>>
>>
>>
>> On Tue, Mar 12, 2013 at 2:41 PM, Robert Sedzik <robert.sedzik at uadm.uu.se> wrote:
>>> Hi all,
>>>
>>> It is possible to move the tomcat/components folder to another location
>>> and start sakai
>>> via a jvm/tomcat switch or by other means to set an alternate
>>> tomcat/components path?
>>>
>>> I have not been able to find a sakai property (sakai.properties)
>>> so I have been trying to do it via code. Changing in sakai kernel with
>>> no success so far.
>>> I am assuming because of tomcat/lib dependencies (spring).
>>>
>>> Cheers,
>>> Robert
>>>
>>>
>>>
>>> _______________________________________________
>>> 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"
>>
>>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 12 Mar 2013 12:45:34 -0700 (PDT)
> From: SamuelGJ <samuelgutierrezjimenez at gmail.com>
> Subject: [Building Sakai] ADD new templates to FCKeditor
> To: sakai-dev at collab.sakaiproject.org
> Message-ID: <1363117534735-7587043.post at n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi all,
>
> I saw that the editor (*FCKEditor*), offers a number of templates:
>
> -> Image and Title
>
> -> Strange Template
>
> -> Text and Table
>
> It would be to change those templates and add various templates, but I can
> not find exactly the file you should modify.
>
> I found a file called *fcktemplates.xml* in
> *Tomcat/webapps/library/editor/FCKeditor*, I trying to modify a template but
> when reloading Sakai, but change is not loaded.
>
> Where could find the file or files to change the default templates of
> FCKeditor?
>
> Thanks in advance.
>
> Regards, Samuel.
>
>
>
> --
> View this message in context: http://sakai-project-mail-list-archives.1343168.n2.nabble.com/ADD-new-templates-to-FCKeditor-tp7587043.html
> Sent from the DG: Development / Buidling Sakai (sakai-dev at collab.sakaiproject.org) mailing list archive at Nabble.com.
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 12 Mar 2013 13:28:48 -0700 (PDT)
> From: SamuelGJ <samuelgutierrezjimenez at gmail.com>
> Subject: Re: [Building Sakai] Sakai 2.9.1 and tomcat 7
> To: sakai-dev at collab.sakaiproject.org
> Message-ID: <1363120128777-7587050.post at n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Fatemeh,
>
> To boot the Sakai version 2.9.1, you should use the version of Tomcat 7.
> That may cause your error.
>
> I let the installation link Sakai 2.9:
>
> *https://confluence.sakaiproject.org/pages/viewpage.action?pageId=82249316*
>
> And to download the version of Tomcat 7:
>
> *http://archive.apache.org/dist/tomcat/*
>
> where you can find different versions of Tomcat, so far.
>
> I think that you can fix your error. If not solved, please ask again.
>
> Regards, Samuel.
>
>
>
> --
> View this message in context: http://sakai-project-mail-list-archives.1343168.n2.nabble.com/Building-Sakai-Sakai-2-9-1-and-tomcat-7-tp7587036p7587050.html
> Sent from the DG: Development / Buidling Sakai (sakai-dev at collab.sakaiproject.org) mailing list archive at Nabble.com.
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 13 Mar 2013 08:34:32 +1100
> From: Steve Swinsburg <steve.swinsburg at gmail.com>
> Subject: Re: [Building Sakai] Deploying Sakai 2.9.1 on Linux , tomcat7
> and Oracle10g
> To: Fatemeh Asl <aa2821 at nyumc.org>
> Cc: "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID: <605D6C4A-5F7B-46F0-A70B-68D456EFD165 at gmail.com>
> Content-Type: text/plain; charset=utf-8
>
> Hi
>
> You have class not found errors with entitybroker. Do you have duplicates in shared lib, perhaps an upgrade from an old install? What settings did you add to Catalina.properties?
>
> Cheers
> Steve
>
> Gesendent von meinem iPhone
>
> On 13/03/2013, at 4:59, Fatemeh Asl <aa2821 at nyumc.org> wrote:
>
>> Sorry for the incomplete post, I meant to add this on top the log:
>>
>> Hi,
>>
>> I downloaded a fresh version of 2.9.1 tag and tried to deploy it.
>> Even though I changed my tomcat 7 to
>> tomcat 5 look,. when I deployed sakai to a clean TC, I got tones of
>> org.apache.catalina.LifecycleException: Failed to start component ? .
>> I am not sure if this a problem with TC, since it seems to work fine:
>>
>> -bash-3.2$ ./bin/startup.sh
>> Using CATALINA_BASE: /cube/apps/sakai_2-9/tomcat
>> Using CATALINA_HOME: /cube/apps/sakai_2-9/tomcat
>> Using CATALINA_TMPDIR: /cube/apps/sakai_2-9/tomcat/temp
>> Using JRE_HOME: /cube/apps/jdk1.6.0_21
>> Using CLASSPATH: /cube/apps/sakai_2-9/tomcat
>> /bin/bootstrap.jar:/cube/apps/sakai_2-
>> 9/tomcat/bin/tomcat-juli.jar
>>
>> Please look at log file I posted before.
>>
>> Many Thanks
>> Fatemeh
>>
>>
>>
>> _______________________________________________
>> 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"
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 13 Mar 2013 09:55:17 +1100
> From: Steve Swinsburg <steve.swinsburg at gmail.com>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Gregory Guthrie <guthrie at mum.edu>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID: <BBBE4F07-CA04-45EA-A621-D993FC957E39 at gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> What is the editor that your Moodle environment uses, can you send a screenshot?
>
> Gesendent von meinem iPhone
>
> On 13/03/2013, at 4:17, Gregory Guthrie <guthrie at mum.edu> wrote:
>
>> I wanted to again give a virtual "vote" for a spelling correction system in the forum & content editor, currently CKEditor.
>> [SAK-23280 add spelling correction options to content editor]
>>
>> Currently a user sees spelling errors as typing (from the browser I presume?), but the standard windows option of right-click suggestions/corrections does not work. This doesn't conform to general Windows or UI standards, and thus surprises those users, since that is a general norm.
>>
>> While it is true that CKE does support plugins for ad-supported spell-while you type, the non-ad version is $3500/year - pretty expensive for a basic feature like this. Perhaps big schools don't much mind or notice such costs, but for smaller users it is significant.
>>
>> I'd also note that our Moodle users, who of course were reluctant to convert, have a better editor with this feature for free in the community version - makes it harder to compete! :-)
>>
>> If there are other good options, I'd love to learn of them.
>> -------------------------------------------
>>
>> _______________________________________________
>> 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"
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 13 Mar 2013 10:11:16 +1100
> From: Steve Swinsburg <steve.swinsburg at gmail.com>
> Subject: Re: [Building Sakai] Moving tomcat/components folder
> To: Robert Sedzik <robert.sedzik at uadm.uu.se>
> Cc: "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID: <9B5898C6-B8C9-451B-B03C-1FD2B462EF2E at gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> This is interesting, what's the motivation for moving this? We could build it into the build/deploy plugin, the plugin has a list of directories for things anyway.
>
> Cheers
> Steve
>
> Gesendent von meinem iPhone
>
> On 13/03/2013, at 6:27, Robert Sedzik <robert.sedzik at uadm.uu.se> wrote:
>
>> Thanks, I missed that -Dsakai.components.root thing.
>>
>> kernel/component-manager/src/main/java/org/sakaiproject/component/impl/SpringCompMgr.java
>>
>>
>> is actually kernel part I am hacking.
>>
>> Thanks for the fast reply.
>>
>> Rob
>>
>>
>>
>> On 12-Mar-13 8:01 PM, Aaron Zeckoski wrote:
>>> I think that providing a property like
>>> -Dsakai.components.root=/path/to/components on your java (tomcat) OPTS
>>> will allow you to override the default value.
>>>
>>> See loadComponents() in
>>> kernel/component-manager/src/main/java/org/sakaiproject/component/impl/SpringCompMgr.java
>>>
>>> I haven't tried this myself but it looks like it should work based on the code.
>>> Worst case scenario, just change the default in that method.
>>>
>>> NOTE: this is a runtime change only, the build will not be affected by this
>>> -AZ
>>>
>>>
>>>
>>> On Tue, Mar 12, 2013 at 2:41 PM, Robert Sedzik <robert.sedzik at uadm.uu.se> wrote:
>>>> Hi all,
>>>>
>>>> It is possible to move the tomcat/components folder to another location
>>>> and start sakai
>>>> via a jvm/tomcat switch or by other means to set an alternate
>>>> tomcat/components path?
>>>>
>>>> I have not been able to find a sakai property (sakai.properties)
>>>> so I have been trying to do it via code. Changing in sakai kernel with
>>>> no success so far.
>>>> I am assuming because of tomcat/lib dependencies (spring).
>>>>
>>>> Cheers,
>>>> Robert
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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"
>
>
> ------------------------------
>
> Message: 9
> Date: Tue, 12 Mar 2013 17:00:14 -0700
> From: Kevin Takacs <ktakacs at rsmart.com>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Gregory Guthrie <guthrie at mum.edu>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAAr3_5M-cN3cqHbERDaqCy9V69cL-d3KyNN-S1tK+8P+qWLrkQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> A while back we modified the aspell plugin in the FCK editor to use
> Google's spell check service. While getting ready for 2.9 we found someone
> ported the aspell plugin to the ckeditor on their forums, so we added the
> Google spell check code to it. I created the following jira and attached a
> patch for trunk if anyone is interested in checking it out:
>
> https://jira.sakaiproject.org/browse/SAK-23344
>
> On Tue, Mar 12, 2013 at 10:17 AM, Gregory Guthrie <guthrie at mum.edu> wrote:
>
>> I wanted to again give a virtual "vote" for a spelling correction system
>> in the forum & content editor, currently CKEditor.
>> [SAK-23280 add spelling correction options to content editor]
>>
>> Currently a user sees spelling errors as typing (from the browser I
>> presume?), but the standard windows option of right-click
>> suggestions/corrections does not work. This doesn't conform to general
>> Windows or UI standards, and thus surprises those users, since that is a
>> general norm.
>>
>> While it is true that CKE does support plugins for ad-supported
>> spell-while you type, the non-ad version is $3500/year - pretty expensive
>> for a basic feature like this. Perhaps big schools don't much mind or
>> notice such costs, but for smaller users it is significant.
>>
>> I'd also note that our Moodle users, who of course were reluctant to
>> convert, have a better editor with this feature for free in the community
>> version - makes it harder to compete! :-)
>>
>> If there are other good options, I'd love to learn of them.
>> -------------------------------------------
>>
>> _______________________________________________
>> 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"
>>
>
>
>
> --
> Kevin Takacs
> *r**Smart* | Sakai Software Engineer
> ktakacs at rsmart.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/6879d098/attachment-0001.html
>
> ------------------------------
>
> Message: 10
> Date: Tue, 12 Mar 2013 20:45:41 -0500
> From: Gregory Guthrie <guthrie at mum.edu>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Steve Swinsburg <steve.swinsburg at gmail.com>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <08EF9DA445C4B5439C4733E1F35705BA024749F762B6 at MAIL.cs.mum.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> http://docs.moodle.org/23/en/Text_editor
>
> The text editor (sometimes referred to as the 'HTML editor' or even 'TinyMCE') has many icons to assist the user in entering content. Many of these icons and functions should be familiar to anyone who uses a word processor. Some examples of where you will see the text editor include: Editing Section headings, description of an activity, writing an answer to a quiz question or editing the content of many blocks.
> Manage editors
> A site administrator can enable / disable text editors in Settings > Site administration > Plugins > Text editors > Manage editors. By default the TinyMCE HTML editor and plain text area are enabled.
> Spell engine
> [cid:image001.png at 01CE1F62.8F931440]
>
> The TinyMCE HTML editor used by Moodle has Google Spell as its default spell engine (spell-checker). This can be changed by a site administrator in Settings > Site administration > Plugins > Text editors > TinyMCE HTML editor.
>
> If PSpellSpell is selected then aspell 0.50 or later must be installed on your server and the path to aspell set in Settings > Site administration > Server > System Paths.
>
> [cid:image002.png at 01CE1F62.8F931440]
>
>
>
>
>
> [cid:image003.png at 01CE1F62.8F931440]
>
>
>
>> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
>
>>
>
>> What is the editor that your Moodle environment uses, can you send a screenshot?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/93c9aaa9/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.png
> Type: image/png
> Size: 8165 bytes
> Desc: image001.png
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/93c9aaa9/attachment-0003.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image002.png
> Type: image/png
> Size: 134958 bytes
> Desc: image002.png
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/93c9aaa9/attachment-0004.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image003.png
> Type: image/png
> Size: 134298 bytes
> Desc: image003.png
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/93c9aaa9/attachment-0005.png
>
> ------------------------------
>
> Message: 11
> Date: Wed, 13 Mar 2013 14:33:50 +1100
> From: Steve Swinsburg <steve.swinsburg at gmail.com>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Gregory Guthrie <guthrie at mum.edu>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAPyxfbGG=aRr0CBD+EWTBoRULa20WafAtQrbTTfxAdiim7FUog at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> The accessibility people might be able to provide more info but we did
> discuss TinyMCE and IIRC the reason we went with CKeditor was to do with
> accessibility. Probably also the extensions we have for picking files etc.
> That said, accessibility seems to be taken care of:
> http://www.tinymce.com/tryit/accessibility.php
>
> The page you pasted talks about google spell and aspell. We used aspell in
> FCKeditor and it was a bit buggy, might have been the plugin though. I'm
> interested to know more about the google spell one, sounds like it might be
> a goer. As long as it fails gracefully when remote connection is
> unavailable.
>
> cheers,
> Steve
>
>
> On Wed, Mar 13, 2013 at 12:45 PM, Gregory Guthrie <guthrie at mum.edu> wrote:
>
>> http://docs.moodle.org/23/en/Text_editor ****
>>
>> The text editor (sometimes referred to as the 'HTML editor' or even
>> 'TinyMCE') has many icons to assist the user in entering content. Many of
>> these icons and functions should be familiar to anyone who uses a word
>> processor. Some examples of where you will see the text editor include:
>> Editing Section headings, description of an activity, writing an answer to
>> a quiz question or editing the content of many blocks.****
>>
>> *Manage editors*
>>
>> A site administrator can enable / disable text editors in *Settings >
>> Site administration > Plugins > Text editors > Manage editors*. By
>> default the TinyMCE HTML editor and plain text area are enabled. ****
>> Spell engine****
>>
>> ****
>>
>> The TinyMCE HTML editor used by Moodle has Google Spell as its default
>> spell engine (spell-checker). This can be changed by a site administrator
>> in *Settings > Site administration > Plugins > Text editors > TinyMCE
>> HTML editor*. ****
>>
>> If PSpellSpell is selected then aspell 0.50 or later must be installed on
>> your server and the path to aspell set in Settings > Site administration >
>> Server > System Paths. ****
>>
>> ****
>>
>> ** **
>>
>> ** **
>>
>> ****
>>
>> ** **
>>
>> > Subject: Re: [Building Sakai] CKEditor & Spelling correction.
>>
>> >
>>
>> > What is the editor that your Moodle environment uses, can you send a
>> screenshot?
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/648db316/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 134298 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/648db316/attachment-0003.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 134958 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/648db316/attachment-0004.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 8165 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/648db316/attachment-0005.png
>
> ------------------------------
>
> Message: 12
> Date: Tue, 12 Mar 2013 22:53:50 -0700
> From: John Bush <john.bush at rsmart.com>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Steve Swinsburg <steve.swinsburg at gmail.com>
> Cc: Gregory Guthrie <guthrie at mum.edu>,
> "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAKCViMPwgf9vp0T01_Thzh3pdUqWeR16yVqgpt8va18Ma07i5A at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> The google one doesn't require a third party install or any costs. The
> library is Apache 2.0, and the only risk is that the google service is
> unavailable (in which case you just won't get any corrections, which seems
> like low risk considering the use case, and the provider is google).
> Another advantage is that it has decent i18n support out of the gate, its
> capturing the sakai locale from ResourceLoader and sending that over to the
> google call, and Kevin already built it, so its ready to go.
>
>
> On Tue, Mar 12, 2013 at 8:33 PM, Steve Swinsburg
> <steve.swinsburg at gmail.com>wrote:
>
>> The accessibility people might be able to provide more info but we did
>> discuss TinyMCE and IIRC the reason we went with CKeditor was to do with
>> accessibility. Probably also the extensions we have for picking files etc.
>> That said, accessibility seems to be taken care of:
>> http://www.tinymce.com/tryit/accessibility.php
>>
>> The page you pasted talks about google spell and aspell. We used aspell in
>> FCKeditor and it was a bit buggy, might have been the plugin though. I'm
>> interested to know more about the google spell one, sounds like it might be
>> a goer. As long as it fails gracefully when remote connection is
>> unavailable.
>>
>> cheers,
>> Steve
>>
>>
>> On Wed, Mar 13, 2013 at 12:45 PM, Gregory Guthrie <guthrie at mum.edu> wrote:
>>
>>> http://docs.moodle.org/23/en/Text_editor ****
>>>
>>> The text editor (sometimes referred to as the 'HTML editor' or even
>>> 'TinyMCE') has many icons to assist the user in entering content. Many of
>>> these icons and functions should be familiar to anyone who uses a word
>>> processor. Some examples of where you will see the text editor include:
>>> Editing Section headings, description of an activity, writing an answer to
>>> a quiz question or editing the content of many blocks.****
>>>
>>> *Manage editors*
>>>
>>> A site administrator can enable / disable text editors in *Settings >
>>> Site administration > Plugins > Text editors > Manage editors*. By
>>> default the TinyMCE HTML editor and plain text area are enabled. ****
>>> Spell engine****
>>>
>>> ****
>>>
>>> The TinyMCE HTML editor used by Moodle has Google Spell as its default
>>> spell engine (spell-checker). This can be changed by a site administrator
>>> in *Settings > Site administration > Plugins > Text editors > TinyMCE
>>> HTML editor*. ****
>>>
>>> If PSpellSpell is selected then aspell 0.50 or later must be installed on
>>> your server and the path to aspell set in Settings > Site administration >
>>> Server > System Paths. ****
>>>
>>> ****
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> ****
>>>
>>> ** **
>>>
>>> > Subject: Re: [Building Sakai] CKEditor & Spelling correction.
>>>
>>> >
>>>
>>> > What is the editor that your Moodle environment uses, can you send a
>>> screenshot?
>>>
>>
>>
>> _______________________________________________
>> 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"
>>
>
>
>
> --
> John Bush
> 602-490-0470
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/053b225c/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 8165 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/053b225c/attachment-0003.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 134298 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/053b225c/attachment-0004.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 134958 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130312/053b225c/attachment-0005.png
>
> ------------------------------
>
> Message: 13
> Date: Wed, 13 Mar 2013 11:27:34 +0530
> From: prabhu <prabhu142003 at gmail.com>
> Subject: [Building Sakai] Reg : Sakai 2.9.2 google docs inetgration
> To: production at collab.sakaiproject.org,
> sakai-dev at collab.sakaiproject.org
> Message-ID:
> <CAEs_ZqzDMgf3L+=--EdfDu3nR8x2fr1Xjvnvx3e5jEC3n45FNA at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> I want to integrate Sakai 2.9.2 with Google Docs. If anyone has
> the proper link or previously project on the same, please do help me...
>
>
>
>
> --
> *
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Regards:
>
> Prabhu Janakaraj,
> Consultant Linux and Networking - Training and Deployment,
> Skype: prabhu.j4
> Handphone: 091 9790 382 999
> *
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/571f9fe8/attachment-0001.html
>
> ------------------------------
>
> Message: 14
> Date: Wed, 13 Mar 2013 09:28:09 +0000
> From: Adrian Fish <adrian.r.fish at gmail.com>
> Subject: [Building Sakai] Returning JSON from createEntity
> To: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAM0rk3FkG8Vt+ht6aY1dJAK0wQzHupyNjowLaB_ARkRFYeqPyQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi all,
>
> Does anybody know how to return JSON from createEntity in an entity
> provider? I know you can craft it; I mean by returning a POJO and having it
> serialized by the framework.
>
> Cheers,
> Adrian.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/2453314b/attachment-0001.html
>
> ------------------------------
>
> Message: 15
> Date: Wed, 13 Mar 2013 12:32:11 +0200
> From: David Wafula <davidwaf at gmail.com>
> Subject: [Building Sakai] Sharing Resources across courses in 2.8.0
> To: Sakai Developers <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAK9Ws2c3C1tT47E-RcupFDzY3iPwg8BNC7J3XtNKr7G4zyTQ_w at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dear all,
> Is it possible to share Resources contents between 2 or more courses,
> without having students as members in all the courses in question.
> Use case:
> A lecturer has courses A, B, C, each with different students.
> Now, the lecturer would want to re-use some content from A in B and so on
> for student access. Can Resources in A be shared with B and C ?
>
> Regards
> --
> David Wafula
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/04c9408a/attachment-0001.html
>
> ------------------------------
>
> Message: 16
> Date: Wed, 13 Mar 2013 12:35:34 +0200
> From: Nguni Phakela <nguni52 at gmail.com>
> Subject: Re: [Building Sakai] Returning JSON from createEntity
> To: Adrian Fish <adrian.r.fish at gmail.com>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAFMpJW1ECb1-bC7W+5wMbDpqHn=hRurX0PoFQr3XODOO13rxQQ at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Adrian,
>
> I'm not sure if this is possible to do using the framework, but I use GSON (
> https://code.google.com/p/google-gson/). It converts between POJO's (or
> list of) and JSON.
>
> Cheers,
> Nguni
>
>
> On Wed, Mar 13, 2013 at 11:28 AM, Adrian Fish <adrian.r.fish at gmail.com>wrote:
>
>> Hi all,
>>
>> Does anybody know how to return JSON from createEntity in an entity
>> provider? I know you can craft it; I mean by returning a POJO and having it
>> serialized by the framework.
>>
>> Cheers,
>> Adrian.
>>
>> _______________________________________________
>> 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"
>>
>
>
>
> --
> Nguni Phakela
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/d9d7adcf/attachment-0001.html
>
> ------------------------------
>
> Message: 17
> Date: Wed, 13 Mar 2013 10:37:55 +0000
> From: Adam Marshall <adam.marshall at it.ox.ac.uk>
> Subject: Re: [Building Sakai] Sharing Resources across courses in
> 2.8.0
> To: David Wafula <davidwaf at gmail.com>, Sakai Developers
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <E1E435A461EE4E479E171D497DD928981943E461 at MBX01.ad.oak.ox.ac.uk>
> Content-Type: text/plain; charset="us-ascii"
>
> No. it would be nice though!
>
> You could make the files public - that would work.
>
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of David Wafula
> Sent: 13 March 2013 10:32
> To: Sakai Developers
> Subject: [Building Sakai] Sharing Resources across courses in 2.8.0
>
> Dear all,
> Is it possible to share Resources contents between 2 or more courses, without having students as members in all the courses in question.
> Use case:
> A lecturer has courses A, B, C, each with different students.
> Now, the lecturer would want to re-use some content from A in B and so on for student access. Can Resources in A be shared with B and C ?
>
> Regards
> --
> David Wafula
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/28357742/attachment-0001.html
>
> ------------------------------
>
> Message: 18
> Date: Wed, 13 Mar 2013 12:40:20 +0200
> From: David Wafula <davidwaf at gmail.com>
> Subject: Re: [Building Sakai] Sharing Resources across courses in
> 2.8.0
> To: Adam Marshall <adam.marshall at it.ox.ac.uk>
> Cc: Sakai Developers <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAK9Ws2f6ttRQO5OYRvF_5nHATo7Zs0P=DG6k0c7SqKTrgvOZjQ at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Ok sure. We were thinking of the public option too.
> Regards
>
>
> On Wed, Mar 13, 2013 at 12:37 PM, Adam Marshall
> <adam.marshall at it.ox.ac.uk>wrote:
>
>> No. it would be nice though!****
>>
>> ** **
>>
>> You could make the files public ? that would work.****
>>
>> ** **
>>
>> *From:* sakai-dev-bounces at collab.sakaiproject.org [mailto:
>> sakai-dev-bounces at collab.sakaiproject.org] *On Behalf Of *David Wafula
>> *Sent:* 13 March 2013 10:32
>> *To:* Sakai Developers
>> *Subject:* [Building Sakai] Sharing Resources across courses in 2.8.0****
>>
>> ** **
>>
>> Dear all,****
>>
>> Is it possible to share Resources contents between 2 or more courses,
>> without having students as members in all the courses in question.****
>>
>> Use case:****
>>
>> A lecturer has courses A, B, C, each with different students.****
>>
>> Now, the lecturer would want to re-use some content from A in B and so on
>> for student access. Can Resources in A be shared with B and C ?
>> ****
>>
>> ** **
>>
>> Regards****
>>
>> --
>> David Wafula ****
>>
>
>
>
> --
> David Wafula
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/fd8e5900/attachment-0001.html
>
> ------------------------------
>
> Message: 19
> Date: Wed, 13 Mar 2013 10:47:01 +0000
> From: Adam Marshall <adam.marshall at it.ox.ac.uk>
> Subject: Re: [Building Sakai] Sharing Resources across courses in
> 2.8.0
> To: David Wafula <davidwaf at gmail.com>
> Cc: Sakai Developers <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <E1E435A461EE4E479E171D497DD928981943E4C5 at MBX01.ad.oak.ox.ac.uk>
> Content-Type: text/plain; charset="us-ascii"
>
> One thing that would also be nice is to add a "display file / folder to all logged in users" option on a Resource's Edit Details page just above the "make public" option. This would be a .auth option to supplement the incumbent .anon option.
>
> adam
>
> From: David Wafula [mailto:davidwaf at gmail.com]
> Sent: 13 March 2013 10:40
> To: Adam Marshall
> Cc: Sakai Developers
> Subject: Re: [Building Sakai] Sharing Resources across courses in 2.8.0
>
> Ok sure. We were thinking of the public option too.
> Regards
>
> On Wed, Mar 13, 2013 at 12:37 PM, Adam Marshall <adam.marshall at it.ox.ac.uk<mailto:adam.marshall at it.ox.ac.uk>> wrote:
> No. it would be nice though!
>
> You could make the files public - that would work.
>
> From: sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org> [mailto:sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org>] On Behalf Of David Wafula
> Sent: 13 March 2013 10:32
> To: Sakai Developers
> Subject: [Building Sakai] Sharing Resources across courses in 2.8.0
>
> Dear all,
> Is it possible to share Resources contents between 2 or more courses, without having students as members in all the courses in question.
> Use case:
> A lecturer has courses A, B, C, each with different students.
> Now, the lecturer would want to re-use some content from A in B and so on for student access. Can Resources in A be shared with B and C ?
>
> Regards
> --
> David Wafula
>
>
>
> --
> David Wafula
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/43894d95/attachment-0001.html
>
> ------------------------------
>
> Message: 20
> Date: Wed, 13 Mar 2013 10:52:03 +0000
> From: Fatima Rahiman <Fatima.Rahiman at wits.ac.za>
> Subject: [Building Sakai] sharing Resources on SAKAI , , , and images
> in Question Pool
> To: "Sakai Developers (sakai-dev at collab.sakaiproject.org)"
> <sakai-dev at collab.sakaiproject.org>,
> "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "samigo-team at collab.sakaiproject.org"
> <samigo-team at collab.sakaiproject.org>
> Cc: Nkululeko Phakela <Nkululeko.Phakela at wits.ac.za>, Tom Waspe
> <Tom.Waspe at wits.ac.za>
> Message-ID:
> <D2CB43055324184499E88ED7124065D227431CF3 at Elpis.ds.WITS.AC.ZA>
> Content-Type: text/plain; charset="us-ascii"
>
> Dear All
>
> We have request from a lecturer to have documents uploaded to Course 1 made available to Course 2 (which has a different cohort of students).
>
> I understand the way around this is that the file settings would then have to reflect the option "This file is publicly viewable" which means all and sundry have access to this resource.
> In other words students could thus send the link to other students which would constitute a security risk if the file is meant to be used in Test and Quizzes instance.
> The latter aspect of security breaches refers to images..which we're also currently having a problem with as once they're uploaded to a question pool (where does the iamge file for the question Pool reside reside btw)or imported from a previous year courses , the new student can't see these images although the instructor is able to. )
> My understanding was that the ability to share files was one of the nice to have options of SAKAI i.e. the ability to share resources across courses etc. ..but if it is only available through making it public then it defeats our needed purpose of a specific group needing to view /access this resource and not everyone (and which by the way is not covered under the "Display this file to selected groups only" as this pertains to groups in the same class) .
>
> Or have we just not enabled a particular setting...?We're running SAKAI 2.8
> Any comments will be highly appreciated!
> Ta
> [cid:image001.png at 01CE1FE9.8F43A860]
>
>
> <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;">
> <tr>
> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td>
> </tr>
> </table
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/cf0fe495/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.png
> Type: image/png
> Size: 15902 bytes
> Desc: image001.png
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/cf0fe495/attachment-0001.png
>
> ------------------------------
>
> Message: 21
> Date: Wed, 13 Mar 2013 12:12:54 +0100
> From: Robert Sedzik <robert.sedzik at uadm.uu.se>
> Subject: Re: [Building Sakai] sharing Resources on SAKAI , , , and
> images in Question Pool
> To: Fatima Rahiman <Fatima.Rahiman at wits.ac.za>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>, Nkululeko Phakela
> <Nkululeko.Phakela at wits.ac.za>, Tom Waspe <Tom.Waspe at wits.ac.za>,
> "Sakai Developers \(sakai-dev at collab.sakaiproject.org\)"
> <sakai-dev at collab.sakaiproject.org>,
> "samigo-team at collab.sakaiproject.org"
> <samigo-team at collab.sakaiproject.org>
> Message-ID: <51405F36.3040609 at uadm.uu.se>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Dear Fatima,
>
> My university has the exact same problem and I have posted on this list
> about it.
>
> There is a Jira issue which relates to this
>
> https://jira.sakaiproject.org/browse/SAM-1596
>
> Cheers,
> Robert
>
>
>
>
> Fatima Rahiman skrev 2013-03-13 11:52:
>>
>> Dear All
>>
>> We have request from a lecturer to have documents uploaded to Course 1
>> made available to Course 2 (which has a different cohort of students).
>>
>> I understand the way around this is that the file settings would then
>> have to reflect the option "|*This file is publicly viewable" *||which
>> means all and sundry have access to this resource||*.*|
>>
>> In other words students could thus send the link to other students
>> which would constitute a security risk if the file is meant to be used
>> in Test and Quizzes instance.
>>
>> The latter aspect of security breaches refers to images..which we're
>> also currently having a problem with as once they're uploaded to a
>> question pool (where does the iamge file for the question Pool reside
>> reside btw)or imported from a previous year courses , the new student
>> can't see these images although the instructor is able to. )
>>
>> My understanding was that the ability to share files was one of the
>> nice to have options of SAKAI i.e. the ability to share resources
>> across courses etc. ..but if it is only available through making it
>> public then it defeats our needed purpose of a specific group
>> needing to view /access this resource and not everyone (and which by
>> the way is not covered under the "|*Display this file to selected
>> groups only" *||as this pertains to groups in the /same / class) .|
>>
>> ||
>>
>> |Or have we just not enabled a particular setting...?We're running
>> SAKAI 2.8|
>>
>> |Any comments will be highly appreciated!|
>>
>> Ta
>>
>> This communication is intended for the addressee only. It is
>> confidential. If you have received this communication in error, please
>> notify us immediately and destroy the original message. You may not
>> copy or disseminate this communication without the permission of the
>> University. Only authorised signatories are competent to enter into
>> agreements on behalf of the University and recipients are thus advised
>> that the content of this message may not be legally binding on the
>> University and may contain the personal views and opinions of the
>> author, which are not necessarily the views and opinions of The
>> University of the Witwatersrand, Johannesburg. All agreements between
>> the University and outsiders are subject to South African Law unless
>> the University agrees in writing to the contrary.
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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/20130313/70bb710d/attachment-0001.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/png
> Size: 15902 bytes
> Desc: not available
> Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/70bb710d/attachment-0001.png
>
> ------------------------------
>
> Message: 22
> Date: Wed, 13 Mar 2013 22:17:16 +1100
> From: Steve Swinsburg <steve.swinsburg at gmail.com>
> Subject: Re: [Building Sakai] Sharing Resources across courses in
> 2.8.0
> To: Adam Marshall <adam.marshall at it.ox.ac.uk>
> Cc: Sakai Developers <sakai-dev at collab.sakaiproject.org>
> Message-ID: <9B09BDF3-33DF-431D-B90D-3ACEF0F2B10C at gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> I jira'd and worked on this here:
> https://jira.sakaiproject.org/browse/SAK-18397
>
> I may be able to dig up that patch though it wasn't complete. That section of resources is very hairy.
>
> cheers,
> Steve
>
>
> On 13/03/2013, at 9:47 PM, Adam Marshall <adam.marshall at it.ox.ac.uk> wrote:
>
>> One thing that would also be nice is to add a ?display file / folder to all logged in users? option on a Resource?s Edit Details page just above the ?make public? option. This would be a .auth option to supplement the incumbent .anon option.
>>
>> adam
>>
>> From: David Wafula [mailto:davidwaf at gmail.com]
>> Sent: 13 March 2013 10:40
>> To: Adam Marshall
>> Cc: Sakai Developers
>> Subject: Re: [Building Sakai] Sharing Resources across courses in 2.8.0
>>
>> Ok sure. We were thinking of the public option too.
>> Regards
>>
>>
>> On Wed, Mar 13, 2013 at 12:37 PM, Adam Marshall <adam.marshall at it.ox.ac.uk> wrote:
>> No. it would be nice though!
>>
>> You could make the files public ? that would work.
>>
>> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of David Wafula
>> Sent: 13 March 2013 10:32
>> To: Sakai Developers
>> Subject: [Building Sakai] Sharing Resources across courses in 2.8.0
>>
>> Dear all,
>> Is it possible to share Resources contents between 2 or more courses, without having students as members in all the courses in question.
>> Use case:
>> A lecturer has courses A, B, C, each with different students.
>> Now, the lecturer would want to re-use some content from A in B and so on for student access. Can Resources in A be shared with B and C ?
>>
>> Regards
>> --
>> David Wafula
>>
>>
>>
>> --
>> David Wafula
>> _______________________________________________
>> 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/20130313/55747cda/attachment-0001.html
>
> ------------------------------
>
> Message: 23
> Date: Wed, 13 Mar 2013 11:40:27 +0000
> From: Adrian Fish <adrian.r.fish at gmail.com>
> Subject: Re: [Building Sakai] Returning JSON from createEntity
> To: Nguni Phakela <nguni52 at gmail.com>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAM0rk3HcVfY81tch5jG9MVogUvJOA11s0UAWn-U30MREeHSNdg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Thanks, I've not heard of that one. I'll take a look at it.
>
> Cheers,
> Adrian.
>
>
> On 13 March 2013 10:35, Nguni Phakela <nguni52 at gmail.com> wrote:
>
>> Hi Adrian,
>>
>> I'm not sure if this is possible to do using the framework, but I use GSON
>> (https://code.google.com/p/google-gson/). It converts between POJO's (or
>> list of) and JSON.
>>
>> Cheers,
>> Nguni
>>
>>
>> On Wed, Mar 13, 2013 at 11:28 AM, Adrian Fish <adrian.r.fish at gmail.com>wrote:
>>
>>> Hi all,
>>>
>>> Does anybody know how to return JSON from createEntity in an entity
>>> provider? I know you can craft it; I mean by returning a POJO and having it
>>> serialized by the framework.
>>>
>>> Cheers,
>>> Adrian.
>>>
>>> _______________________________________________
>>> 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"
>>>
>>
>>
>>
>> --
>> Nguni Phakela
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/37d9c47d/attachment-0001.html
>
> ------------------------------
>
> Message: 24
> Date: Wed, 13 Mar 2013 08:22:32 -0400
> From: Aaron Zeckoski <azeckoski at unicon.net>
> Subject: Re: [Building Sakai] Returning JSON from createEntity
> To: Adrian Fish <adrian.r.fish at gmail.com>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAMTQKL=tpmO6qLxmpdP5STpOwLRvrLujh_cjnDWbGBkNG109SA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> There's a JSON encoder in the EB reflect utils. I tried GSON and found
> it did not handle things like maps correctly. It worked OK for POJOs
> (unless they contained something like a map or an array).
>
> -AZ
>
>
> On Wed, Mar 13, 2013 at 5:28 AM, Adrian Fish <adrian.r.fish at gmail.com> wrote:
>> Hi all,
>>
>> Does anybody know how to return JSON from createEntity in an entity
>> provider? I know you can craft it; I mean by returning a POJO and having it
>> serialized by the framework.
>>
>> Cheers,
>> Adrian.
>>
>> _______________________________________________
>> 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"
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
>
> ------------------------------
>
> Message: 25
> Date: Wed, 13 Mar 2013 12:41:24 +0000
> From: Adrian Fish <adrian.r.fish at gmail.com>
> Subject: Re: [Building Sakai] Returning JSON from createEntity
> To: Aaron Zeckoski <azeckoski at unicon.net>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAM0rk3E4pN_5OXL3ViDHtummDEyU6Ao15WKVxcECOAgZHMjqmw at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Aaron,
>
> What I'd like to do though is just return an object from the createEntity
> method, rather than a String, and have it encoded automagically. I'd rather
> not explicitly call methods to produce my JSON and then return it. Is there
> any particular reason only a String can be returned from createEntity?
>
> Cheers,
> Adrian.
>
>
> On 13 March 2013 12:22, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>
>> There's a JSON encoder in the EB reflect utils. I tried GSON and found
>> it did not handle things like maps correctly. It worked OK for POJOs
>> (unless they contained something like a map or an array).
>>
>> -AZ
>>
>>
>> On Wed, Mar 13, 2013 at 5:28 AM, Adrian Fish <adrian.r.fish at gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > Does anybody know how to return JSON from createEntity in an entity
>> > provider? I know you can craft it; I mean by returning a POJO and having
>> it
>> > serialized by the framework.
>> >
>> > Cheers,
>> > Adrian.
>> >
>> > _______________________________________________
>> > 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"
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/fbfb9a9b/attachment-0001.html
>
> ------------------------------
>
> Message: 26
> Date: Wed, 13 Mar 2013 09:12:00 -0400
> From: Aaron Zeckoski <azeckoski at unicon.net>
> Subject: Re: [Building Sakai] Returning JSON from createEntity
> To: Adrian Fish <adrian.r.fish at gmail.com>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAMTQKLmNNGZOuPnt1Y2qvNMufGWvv_DMHZ5XJdUj2YwkDWW4Tw at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Mostly that was just to adhere to the microformat. I suppose that I
> could change it in trunk but it would mean an API change which could
> affect all implemented providers.
>
> -AZ
>
>
> On Wed, Mar 13, 2013 at 8:41 AM, Adrian Fish <adrian.r.fish at gmail.com> wrote:
>> Hi Aaron,
>>
>> What I'd like to do though is just return an object from the createEntity
>> method, rather than a String, and have it encoded automagically. I'd rather
>> not explicitly call methods to produce my JSON and then return it. Is there
>> any particular reason only a String can be returned from createEntity?
>>
>> Cheers,
>> Adrian.
>>
>>
>> On 13 March 2013 12:22, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>>>
>>> There's a JSON encoder in the EB reflect utils. I tried GSON and found
>>> it did not handle things like maps correctly. It worked OK for POJOs
>>> (unless they contained something like a map or an array).
>>>
>>> -AZ
>>>
>>>
>>> On Wed, Mar 13, 2013 at 5:28 AM, Adrian Fish <adrian.r.fish at gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Does anybody know how to return JSON from createEntity in an entity
>>> > provider? I know you can craft it; I mean by returning a POJO and having
>>> > it
>>> > serialized by the framework.
>>> >
>>> > Cheers,
>>> > Adrian.
>>> >
>>> > _______________________________________________
>>> > 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"
>>>
>>>
>>>
>>> --
>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>
>>
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
>
> ------------------------------
>
> Message: 27
> Date: Wed, 13 Mar 2013 14:40:33 +0000 (UTC)
> From: Fatemeh Asl <aa2821 at nyumc.org>
> Subject: Re: [Building Sakai] Sakai 2.9.1 and tomcat 7
> To: sakai-dev at collab.sakaiproject.org
> Message-ID: <loom.20130313T152528-162 at post.gmane.org>
> Content-Type: text/plain; charset=us-ascii
>
> SamuelGJ <samuelgutierrezjimenez <at> gmail.com> writes:
>
> Samuel,
>
> Thanks.
>
> I downloaded the sakai release archive and and TC7 from the specified links. But
> it gives me the following dependency error:
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Sakai Master ......................................
> SUCCESS [0.329s]
> [INFO] Sakai Core Project ................................
> SUCCESS [0.017s]
> [INFO] Sakai Kernel Deploy ...............................
> SUCCESS [18.850s]
> [INFO] Sakai Core Deploy .................................
> FAILURE [1:17.789s]
> [INFO] sakai-jstl-shared-deploy .......................... SKIPPED
> [INFO] Sakai Access Project .............................. SKIPPED
> [INFO] sakai-access-impl ................................. SKIPPED
> [INFO] access ............................................ SKIPPED
> [INFO] web ............................................... SKIPPED
> [INFO] Sakai Alias Project ............................... SKIPPED
> [INFO] sakai-alias-tool .................................. SKIPPED
> [INFO] Sakai Archive Project ............................. SKIPPED
> [INFO] sakai-archive-tool ................................ SKIPPED
> [INFO] Sakai Announcement Import Handlers ................ SKIPPED
> [INFO] Sakai Import Components Package ................... SKIPPED
> [INFO] Sakai AuthZ Project ............................... SKIPPED
> [INFO] sakai-authz-tool .................................. SKIPPED
> [INFO] Sakai Chat Project ................................ SKIPPED
> [INFO] sakai-chat-api .................................... SKIPPED
> [INFO] Sakai Chat Help ................................... SKIPPED
> [INFO] sakai-chat-impl ................................... SKIPPED
> [INFO] sakai-chat-pack ................................... SKIPPED
> [INFO] sakai-chat-tool ................................... SKIPPED
> [INFO] Citations Project ................................. SKIPPED
> [INFO] sakai-citations-api ............................... SKIPPED
> [INFO] sakai-citations-web2bridge ........................ SKIPPED
> [INFO] sakai-citations-util .............................. SKIPPED
> [INFO] sakai-citations-xserver ........................... SKIPPED
> [INFO] sakai-citations-impl .............................. SKIPPED
> [INFO] savecite .......................................... SKIPPED
> [INFO] sakai-citations-tool .............................. SKIPPED
> [INFO] sakai-citations-pack .............................. SKIPPED
> [INFO] sakai-citations-shared-deploy ..................... SKIPPED
> [INFO] Sakai Config Project .............................. SKIPPED
> [INFO] configuration-bundles ............................. SKIPPED
> [INFO] localization-bundles .............................. SKIPPED
> [INFO] localization-pack ................................. SKIPPED
> [INFO] shared-i18n-bundles ............................... SKIPPED
> [INFO] shared-i18n-pack .................................. SKIPPED
> [INFO] Sakai Content Project ............................. SKIPPED
> [INFO] Sakai Content Help ................................ SKIPPED
> [INFO] sakai-content-copyright-api ....................... SKIPPED
> [INFO] sakai-content-copyright-impl ...................... SKIPPED
> [INFO] sakai-content-copyright-pack ...................... SKIPPED
> [INFO] content-providers-impl ............................ SKIPPED
> [INFO] content-providers-pack ............................ SKIPPED
> [INFO] content-bundle .................................... SKIPPED
> [INFO] content-tool ...................................... SKIPPED
> [INFO] content-types ..................................... SKIPPED
> [INFO] Sakai Content Types Component Package ............. SKIPPED
> [INFO] Sakai DAV Project ................................. SKIPPED
> [INFO] sakai-dav-common .................................. SKIPPED
> [INFO] dav ............................................... SKIPPED
> [INFO] sakai-dav-server .................................. SKIPPED
> [INFO] Sakai Gradebook Project ........................... SKIPPED
> [INFO] sakai-gradebook-help .............................. SKIPPED
> [INFO] sakai-gradebook-testservice ....................... SKIPPED
> [INFO] sakai-gradebook-app ............................... SKIPPED
> [INFO] sakai-gradebook-app-business ...................... SKIPPED
> [INFO] sakai-gradebook-app-ui ............................ SKIPPED
> [INFO] sakai-gradebook-tool .............................. SKIPPED
> [INFO] sakai-gradebook-standalone-app .................... SKIPPED
> [INFO] sakai-gradebooksample-grade-converter ............. SKIPPED
> [INFO] Sakai Help Project ................................ SKIPPED
> [INFO] sakai-help-content ................................ SKIPPED
> [INFO] sakai-help-api .................................... SKIPPED
> [INFO] sakai-comp-shared-help ............................ SKIPPED
> [INFO] sakai-comp-help ................................... SKIPPED
> [INFO] sakai-help-tool ................................... SKIPPED
> [INFO] Sakai Link Tool Project ........................... SKIPPED
> [INFO] Sakai Login Project ............................... SKIPPED
> [INFO] sakai-login-api ................................... SKIPPED
> [INFO] authn ............................................. SKIPPED
> [INFO] sakai-login-impl .................................. SKIPPED
> [INFO] login-pack ........................................ SKIPPED
> [INFO] login-render-engine-impl .......................... SKIPPED
> [INFO] login-render ...................................... SKIPPED
> [INFO] sakai-login-tool .................................. SKIPPED
> [INFO] Sakai Memory Project .............................. SKIPPED
> [INFO] sakai-memory-tool ................................. SKIPPED
> [INFO] sakai-metaobj base pom ............................ SKIPPED
> [INFO] sakai-metaobj-api ................................. SKIPPED
> [INFO] sakai-metaobj-help ................................ SKIPPED
> [INFO] sakai-metaobj-tool-lib ............................ SKIPPED
> [INFO] sakai-metaobj-impl ................................ SKIPPED
> [INFO] sakai-metaobj-component ........................... SKIPPED
> [INFO] sakai-metaobj-tool ................................ SKIPPED
> [INFO] sakai-metaobj-assembly ............................ SKIPPED
> [INFO] sakai-metaobj-tool ................................ SKIPPED
> [INFO] Sakai OSP Project ................................. SKIPPED
> [INFO] osp-common ........................................ SKIPPED
> [INFO] OSP Common Service ................................ SKIPPED
> [INFO] OSP Common Implementation ......................... SKIPPED
> [INFO] OSP Common Component .............................. SKIPPED
> [INFO] OSP Common Tool Lib ............................... SKIPPED
> [INFO] osp-jsf ........................................... SKIPPED
> [INFO] OSP JSF Widgets ................................... SKIPPED
> [INFO] Sakai OSP JSF Widgets Dependencies for Sun RI ..... SKIPPED
> [INFO] OSP Common Tool ................................... SKIPPED
> [INFO] OSP Styles Help ................................... SKIPPED
> [INFO] osp-glossary ...................................... SKIPPED
> [INFO] OSP Glossary Service .............................. SKIPPED
> [INFO] OSP Glossary Implementation ....................... SKIPPED
> [INFO] OSP Glossary Component ............................ SKIPPED
> [INFO] OSP Glossary Tool Lib ............................. SKIPPED
> [INFO] OSP Glossary Tool ................................. SKIPPED
> [INFO] OSP Glossary Help ................................. SKIPPED
> [INFO] osp-integration ................................... SKIPPED
> [INFO] OSP Integration with Sakai ........................ SKIPPED
> [INFO] OSP Integration with Sakai Implementation ......... SKIPPED
> [INFO] OSP Integration with Sakai Component .............. SKIPPED
> [INFO] OSP JSF Widgets - Example ......................... SKIPPED
> [INFO] OSP JSF Widgets - Resource ........................ SKIPPED
> [INFO] Sakai OSP JSF Widgets Dependencies for MyFaces .... SKIPPED
> [INFO] OSP Master ........................................ SKIPPED
> [INFO] osp-matrix ........................................ SKIPPED
> [INFO] OSP Matrix Service ................................ SKIPPED
> [INFO] osp-wizard ........................................ SKIPPED
> [INFO] OSP Wizard Service ................................ SKIPPED
> [INFO] sakai-site-manage base pom ........................ SKIPPED
> [INFO] sakai-site-manage-api ............................. SKIPPED
> [INFO] sakai-site-manage-util ............................ SKIPPED
> [INFO] sakai-siteassociation-api ......................... SKIPPED
> [INFO] OSP Matrix Service implementation ................. SKIPPED
> [INFO] OSP Glossary Component ............................ SKIPPED
> [INFO] OSP Matrix Tool ................................... SKIPPED
> [INFO] OSP Matrix Help ................................... SKIPPED
> [INFO] osp-portal-base ................................... SKIPPED
> [INFO] OSP Portal Service ................................ SKIPPED
> [INFO] OSP Portal Implementation ......................... SKIPPED
> [INFO] OSP Portal Component .............................. SKIPPED
> [INFO] OSP Portal ........................................ SKIPPED
> [INFO] OSP Portal ........................................ SKIPPED
> [INFO] osp-presentation .................................. SKIPPED
> [INFO] OSP Presentation Service .......................... SKIPPED
> [INFO] OSP Presentation Service implementation ........... SKIPPED
> [INFO] OSP Presentation Component ........................ SKIPPED
> [INFO] OSP Presentation Tool Lib ......................... SKIPPED
> [INFO] OSP Presentation Tool ............................. SKIPPED
> [INFO] OSP Presentation Layout Help ...................... SKIPPED
> [INFO] sakai-warehouse base pom .......................... SKIPPED
> [INFO] sakai-warehouse-api ............................... SKIPPED
> [INFO] sakai-warehouse-impl .............................. SKIPPED
> [INFO] osp-warehouse ..................................... SKIPPED
> [INFO] OSP Warehouse Implementation ...................... SKIPPED
> [INFO] OSP Warehouse Component ........................... SKIPPED
> [INFO] OSP Wizard Service implementation ................. SKIPPED
> [INFO] OSP Wizard Components ............................. SKIPPED
> [INFO] OSP Wizard Tool Lib ............................... SKIPPED
> [INFO] OSP Wizard Tool ................................... SKIPPED
> [INFO] OSP Wizard Help ................................... SKIPPED
> [INFO] osp-xsltcharon .................................... SKIPPED
> [INFO] xslt portal ....................................... SKIPPED
> [INFO] Sakai Podcast Project ............................. SKIPPED
> [INFO] Sakai Podcasts Help ............................... SKIPPED
> [INFO] sakai-podcasts-api ................................ SKIPPED
> [INFO] sakai-podcasts-impl ............................... SKIPPED
> [INFO] sakai-podcasts-pack ............................... SKIPPED
> [INFO] podcasts .......................................... SKIPPED
> [INFO] sakai-podcasts .................................... SKIPPED
> [INFO] Sakai Postem Project .............................. SKIPPED
> [INFO] sakai-postem-api .................................. SKIPPED
> [INFO] sakai-postem-hbm .................................. SKIPPED
> [INFO] sakai-postem-impl ................................. SKIPPED
> [INFO] sakai-postem-pack ................................. SKIPPED
> [INFO] Sakai Postem Tool ................................. SKIPPED
> [INFO] Sakai Post'Em Help ................................ SKIPPED
> [INFO] Sakai Providers Project ........................... SKIPPED
> [INFO] sakai-allhands-provider ........................... SKIPPED
> [INFO] sakai-coursemanagement-authz-provider-impl ........ SKIPPED
> [INFO] sakai-coursemanagement-authz-provider-impl ........ SKIPPED
> [INFO] sakai-sample-provider ............................. SKIPPED
> [INFO] sakai-hybrid-provider ............................. SKIPPED
> [INFO] sakai-provider-pack ............................... SKIPPED
> [INFO] sakai-federating-provider ......................... SKIPPED
> [INFO] sakai-imsent-provider ............................. SKIPPED
> [INFO] sakai-jldap-provider-mock ......................... SKIPPED
> [INFO] sakai-jldap-provider .............................. SKIPPED
> [INFO] sakai-kerberos-provider ........................... SKIPPED
> [INFO] sakai-openldap-provider ........................... SKIPPED
> [INFO] Sakai TextArea Project ............................ SKIPPED
> [INFO] sakai-fck-connector ............................... SKIPPED
> [INFO] Sakai Library Project ............................. SKIPPED
> [INFO] Sakai Library ..................................... SKIPPED
> [INFO] Sakai Rights Project .............................. SKIPPED
> [INFO] sakai-rights-api .................................. SKIPPED
> [INFO] sakai-rights-impl ................................. SKIPPED
> [INFO] sakai-rights-pack ................................. SKIPPED
> [INFO] sakai-rights-tool ................................. SKIPPED
> [INFO] Sakai Roster Project .............................. SKIPPED
> [INFO] Sakai Roster Service .............................. SKIPPED
> [INFO] Sakai Roster Implementation ....................... SKIPPED
> [INFO] Sakai Roster Components ........................... SKIPPED
> [INFO] Sakai Roster List Tool ............................ SKIPPED
> [INFO] Sakai Roster Help ................................. SKIPPED
> [INFO] Sakai RWiki Project ............................... SKIPPED
> [INFO] sakai-rwiki-api ................................... SKIPPED
> [INFO] sakai-rwiki-help .................................. SKIPPED
> [INFO] sakai-radeox ...................................... SKIPPED
> [INFO] sakai-rwiki-model ................................. SKIPPED
> [INFO] sakai-rwiki-util .................................. SKIPPED
> [INFO] sakai-rwiki-impl .................................. SKIPPED
> [INFO] sakai-rwiki-integration-test ...................... SKIPPED
> [INFO] sakai-rwiki-diff .................................. SKIPPED
> [INFO] sakai-rwiki-pack .................................. SKIPPED
> [INFO] sakai-rwiki-tool .................................. SKIPPED
> [INFO] wiki .............................................. SKIPPED
> [INFO] Sakai Sections Project ............................ SKIPPED
> [INFO] Sakai Section Info Help ........................... SKIPPED
> [INFO] sakai-sections-app-util ........................... SKIPPED
> [INFO] sakai-sections-tool ............................... SKIPPED
> [INFO] sakai-site-pageorder-helper ....................... SKIPPED
> [INFO] sakai-site-pageorder-helper-assembly .............. SKIPPED
> [INFO] sakai-siteassociation-hbm ......................... SKIPPED
> [INFO] sakai-siteassociation-impl ........................ SKIPPED
> [INFO] sakai-siteassociation-pack ........................ SKIPPED
> [INFO] sakai-siteassociation-util ........................ SKIPPED
> [INFO] sakai-siteassociation-tool ........................ SKIPPED
> [INFO] sakai-siteassociation-assembly .................... SKIPPED
> [INFO] sakai-site-manage-hbm ............................. SKIPPED
> [INFO] sakai-site-manage-help ............................ SKIPPED
> [INFO] sakai-site-manage-impl ............................ SKIPPED
> [INFO] sakai-site-manage-pack ............................ SKIPPED
> [INFO] sakai-site-manage-group-section-role-helper-pack .. SKIPPED
> [INFO] sakai-site-manage-group-section-role-helper ....... SKIPPED
> [INFO] sakai-site-manage-link-helper ..................... SKIPPED
> [INFO] sakai-site-manage-participant-helper .............. SKIPPED
> [INFO] sakai-site-manage-tool ............................ SKIPPED
> [INFO] sakai-site-manage-assembly ........................ SKIPPED
> [INFO] sakai-site-manage-group-helper .................... SKIPPED
> [INFO] Sakai Syllabus Project ............................ SKIPPED
> [INFO] Sakai Syllabus API ................................ SKIPPED
> [INFO] sakai-syllabus-hbm ................................ SKIPPED
> [INFO] sakai-syllabus-impl ............................... SKIPPED
> [INFO] sakai-syllabus-pack ............................... SKIPPED
> [INFO] Sakai Syllabus Help ............................... SKIPPED
> [INFO] sakai-syllabus-tool ............................... SKIPPED
> [INFO] Sakai Tool Project ................................ SKIPPED
> [INFO] sakai-tool-tool-su ................................ SKIPPED
> [INFO] Become User Help (su-help) ........................ SKIPPED
> [INFO] Sakai User Project ................................ SKIPPED
> [INFO] sakai-user-tool ................................... SKIPPED
> [INFO] sakai-user-tool-admin-prefs ....................... SKIPPED
> [INFO] sakai-user-tool-prefs ............................. SKIPPED
> [INFO] sakai-warehouse-component ......................... SKIPPED
> [INFO] sakai-warehouse-assembly .......................... SKIPPED
> [INFO] Sakai Web Project ................................. SKIPPED
> [INFO] sakai-news-api .................................... SKIPPED
> [INFO] sakai-news-impl ................................... SKIPPED
> [INFO] sakai-news-pack ................................... SKIPPED
> [INFO] sakai-news-tool ................................... SKIPPED
> [INFO] sakai-web-api ..................................... SKIPPED
> [INFO] Sakai Web Help .................................... SKIPPED
> [INFO] sakai-web-impl .................................... SKIPPED
> [INFO] sakai-web-pack .................................... SKIPPED
> [INFO] sakai-web-tool .................................... SKIPPED
> [INFO] Sakai User Membership Project .................... SKIPPED
> [INFO] sakai-usermembership-api .......................... SKIPPED
> [INFO] sakai-usermembership-help ......................... SKIPPED
> [INFO] sakai-usermembership-impl ......................... SKIPPED
> [INFO] sakai-usermembership-pack ......................... SKIPPED
> [INFO] sakai-usermembership-tool ......................... SKIPPED
> [INFO] ------------------------------------------------
> ------------------------
> [INFO] BUILD FAILURE
> [INFO] -------------------------------------------------
> -----------------------
> [INFO] Total time: 1:39.719s
> [INFO] Finished at: Wed Mar 13 10:15:28 EDT 2013
> [INFO] Final Memory: 125M/495M
> [INFO] ------------------------------------------------
> ------------------------
> [ERROR] Failed to execute goal on project core-deploy: Could not resolve
> dependencies for project org.sakaiproject:core-deploy
> :pom:2.9.0: Failed
> to collect dependencies for [org.sakaiproject.announcement:sakai-
> announcement-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject
> .assignment:sakai-assignment-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.basiclti:basiclti-assembly:zip:tomcat-overlay:2.0.0
> (compile), org.sakaiproject.calendar:sakai-calendar-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.common
> :sakai-common-assembly
> :zip:tomcat-overlay:1.2.0 (compile), org.sakaiproject.
> contentreview:
> sakai-contentreview-assembly:zip:tomcat-overlay:2.9.2 (compile),
> org.sakaiproject.courier:sakai-courier-assembly:zip:
> tomcat-overlay:2.9.0
> (compile), org.sakaiproject.edu-services:edu-services-assembly:
> zip:tomcat-overlay:1.2.0 (compile), org.sakaiproject.
> emailtemplateservice:emailtemplateservice-assembly:
> zip:tomcat-overlay:0.6.0 (compile), org.sakaiproject
> .hybrid:hybrid-assembly:zip:tomcat-overlay:1.2.0 (compile),
> org.sakaiproject.jsf:jsf-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.lessonbuilder:sakai-lessonbuildertool-
> assembly:zip:tomcat-overlay:1.4.0 (compile), org.sakaiproject.
> mailarchive:sakai-mailarchive-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.mailsender:mailsender-assembly:zip:
> tomcat-overlay:1.7.1 (compile), org.sakaiproject.message:sakai
> -message-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject
> .msgcntr:messageforums-assembly:zip:tomcat-overlay:3.0.0 (compile),
> org.sakaiproject.polls:polls-assembly:zip:tomcat-overlay:1.5.0
> (compile), org.sakaiproject.portal:sakai-portal-assembly:zip
> :tomcat-overlay:2.9.0 (compile), org.sakaiproject.presence:sakai
> -presence-assembly:zip:tomcat-overlay:2.9.0 (compile), org.
> sakaiproject.profile:profile-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.profile2:profile2-assembly:zip:
> tomcat-overlay:1.5.0 (compile), org.sakaiproject.reset-pass
> :reset-pass-assembly
> :zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.samigo:samigo-assembly
> :zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.scheduler:scheduler-
> assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.search:search
> -assembly:zip:tomcat-overlay:1.4.0 (compile), org.sakaiproject.shortenedurl:
> shortenedurl-assembly:zip:tomcat-overlay:1.1.0 (compile), org.sakaiproject.
> site:sakai-site-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.sitestats:sitestats-assembly:zip:tomcat-overlay
> :2.3.0 (compile), org.sakaiproject.taggable:sakai-taggable-assembly
> :zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.velocity:sakai
> -velocity-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject
> .webservices:webservices-assembly:zip:tomcat-overlay:1.1.0 (compile),
> junit:junit:jar:3.8.1 (test)]: Failed to read artifact descriptor for
> org.sakaiproject.message:sakai-message-assembly:zip:tomcat-overlay:
> 2.9.0: Could not transfer artifact org.sakaiproject.message:sakai-message
> -assembly:pom:2.9.0 from/to sakai-maven (http://source.sakaiproject.
> org/maven2): Connection reset -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project core-deploy: Could not resolve dependencies for project
> org.sakaiproject:core-deploy:pom:2.9.0: Failed to collect dependencies for
> [org.sakaiproject.announcement:sakai-announcement-assembly:zip:tomcat-over
> lay:2.9.0 (compile), org.sakaiproject.assignment:sakai-
> assignment-assembly
> :zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.basiclti:basiclti-
> assembly:zip:tomcat-overlay:2.0.0 (compile), org.sakaiproject.
> calendar:sakai
> -calendar-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> common:sakai-common-assembly:zip:tomcat-overlay:1.2.0 (compile), org.
> sakaiproject.contentreview:sakai-contentreview-assembly:zip:tomcat-overlay:
> 2.9.2 (compile), org.sakaiproject.courier:sakai-courier-assembly:zip:tomcat
> -overlay:2.9.0 (compile), org.sakaiproject.edu-services:
> edu-services-assembly
> :zip:tomcat-overlay:1.2.0 (compile), org.sakaiproject.emailtemplateservice:
> emailtemplateservice-assembly:zip:tomcat-overlay:0.6.0 (compile),
> org.sakaiproject.hybrid:hybrid-assembly:zip:tomcat-overlay:1.2.0 (compile)
> , org.sakaiproject.jsf:jsf-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.lessonbuilder:sakai-lessonbuildertool-assembly:zip:
> tomcat-overlay:1.4.0 (compile), org.sakaiproject.mailarchive:sakai-
> mailarchive-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject
> .mailsender:mailsender-assembly:zip:tomcat-overlay:1.7.1 (compile),
> org.sakaiproject.message:sakai-message-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.msgcntr:messageforums-assembly:zip:
> tomcat-overlay:3.0.0 (compile), org.sakaiproject.polls:polls-assembly
> :zip:tomcat-overlay:1.5.0 (compile), org.sakaiproject.portal:sakai-
> portal-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> presence:sakai-presence-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.profile:profile-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.profile2:profile2-assembly:zip:tomcat-
> overlay:1.5.0 (compile), org.sakaiproject.reset-pass:
> reset-pass-assembly:
> zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> samigo:samigo-assembly
> :zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.scheduler:scheduler-
> assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.search:search
> -assembly:zip:tomcat-overlay:1.4.0 (compile),
> org.sakaiproject.shortenedurl
> :shortenedurl-assembly:zip:tomcat-overlay:1.1.0 (compile),
> org.sakaiproject
> .site:sakai-site-assembly:zip:tomcat-overlay:2.9.0 (compile), org.
> sakaiproject.sitestats:sitestats-assembly:zip:tomcat-overlay:2.3.0
> (compile), org.sakaiproject.taggable:sakai-taggable-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.velocity:sakai-
> velocity-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject
> .webservices:webservices-assembly:zip:tomcat-overlay:1.1.0 (compile),
> junit:junit:jar:3.8.1 (test)]
> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.
> getDependencies(LifecycleDependencyResolver.java:210)
> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.
> resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependen
> ciesAreResolved(MojoExecutor.java:258)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:201)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
> java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild
> (LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.
> launcher.Launcher.
> launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException:
> Could not resolve dependencies for project org.sakaiproject:core-deploy:
> pom:2.9.0: Failed to collect dependencies for [org.sakaiproject.announcement:
> sakai-announcement-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.assignment:sakai-assignment-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.basiclti:basiclti-assembly:zip:tomcat-overlay:
> 2.0.0 (compile), org.sakaiproject.calendar:sakai-calendar-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.common:
> sakai-common-assembly:zip:tomcat-overlay:1.2.0 (compile),
> org.sakaiproject.contentreview:sakai-contentreview-assembly:
> zip:tomcat-overlay:2.9.2 (compile), org.sakaiproject.courier:
> sakai-courier-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.edu-services:edu-services-assembly:zip:tomcat-overlay:1.2.0
> (compile), org.sakaiproject.emailtemplateservice:
> emailtemplateservice-assembly:zip:tomcat-overlay:0.6.0
> (compile), org.sakaiproject.hybrid:hybrid-assembly:zip:tomcat-overlay:1.2.0
> (compile), org.sakaiproject.jsf:jsf-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.lessonbuilder:
> sakai-lessonbuildertool-assembly:zip:tomcat-overlay:1.4.0 (compile)
> , org.sakaiproject.mailarchive:sakai-mailarchive-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.mailsender:
> mailsender-assembly:zip:tomcat-overlay:1.7.1 (compile),
> org.sakaiproject.message:sakai-message-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.msgcntr:messageforums-assembly:zip:
> tomcat-overlay:3.0.0 (compile), org.sakaiproject.polls:polls-assembly:
> zip:tomcat-overlay:1.5.0 (compile), org.sakaiproject.portal:
> sakai-portal-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.presence:sakai-presence-assembly:zip:tomcat-overlay:
> 2.9.0 (compile), org.sakaiproject.profile:profile-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.profile2:
> profile2-assembly:zip:tomcat-overlay:1.5.0 (compile),
> org.sakaiproject.reset-pass:reset-pass-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.samigo:samigo-assembly:zip:tomcat-overlay:
> 2.9.0 (compile), org.sakaiproject.scheduler:scheduler-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.search:search-assembly
> :zip:tomcat-overlay:1.4.0 (compile), org.sakaiproject.shortenedurl:
> shortenedurl-assembly:zip:tomcat-overlay:1.1.0 (compile),
> org.sakaiproject.site:sakai-site-assembly:zip:tomcat-overlay:2.9.0
> (compile), org.sakaiproject.sitestats:sitestats-assembly:zip:
> tomcat-overlay:2.3.0 (compile), org.sakaiproject.taggable:
> sakai-taggable-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.velocity:sakai-velocity-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.webservices
> :webservices-assembly:zip:tomcat-overlay:1.1.0 (compile),
> junit:junit:jar:3.8.1 (test)]
> at org.apache.maven.project.DefaultProjectDependenciesResolver.
> resolve(DefaultProjectDependenciesResolver.java:158)
> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.
> getDependencies(LifecycleDependencyResolver.java:185)
> ... 22 more
> Caused by: org.sonatype.aether.collection.DependencyCollectionException:
> Failed to collect dependencies for [org.sakaiproject.announcement:
> sakai-announcement-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.assignment:sakai-assignment-assembly:zip:tomcat-
> overlay:2.9.0 (compile), org.sakaiproject.basiclti:basiclti-assembly:
> zip:tomcat-overlay:2.0.0 (compile), org.sakaiproject.calendar:sakai-
> calendar-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> common:sakai-common-assembly:zip:tomcat-overlay:1.2.0 (compile),
> org.sakaiproject.contentreview:sakai-contentreview-assembly:zip
> :tomcat-overlay:2.9.2 (compile), org.sakaiproject.courier:sakai-
> courier-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> edu-services:edu-services-assembly:zip:tomcat-overlay:1.2.0 (compile),
> org.sakaiproject.emailtemplateservice:emailtemplateservice-assembly:zip:
> tomcat-overlay:0.6.0 (compile), org.sakaiproject.hybrid:hybrid-assembly:
> zip:tomcat-overlay:1.2.0 (compile), org.sakaiproject.jsf:jsf-assembly:zip:
> tomcat-overlay:2.9.0 (compile), org.sakaiproject.lessonbuilder:sakai-
> lessonbuildertool-assembly:zip:tomcat-overlay:1.4.0 (compile),
> org.sakaiproject.mailarchive:sakai-mailarchive-assembly:zip:tomcat-overlay:
> 2.9.0
> (compile), org.sakaiproject.mailsender:mailsender-assembly:zip:tomcat-
> overlay:1.7.1 (compile), org.sakaiproject.message:sakai-message-assembly:zip
> :tomcat-overlay:2.9.0 (compile), org.sakaiproject.msgcntr:messageforums-
> assembly:zip:tomcat-overlay:3.0.0 (compile), org.sakaiproject.polls:
> polls-assembly:zip:tomcat-overlay:1.5.0 (compile), org.sakaiproject.portal
> :sakai-portal-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject
> .presence:sakai-presence-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.profile:profile-assembly:zip:tomcat-overlay:2.9.0 (compile)
> , org.sakaiproject.profile2:profile2-assembly:zip:tomcat-overlay:
> 1.5.0 (compile), org.sakaiproject.reset-pass:reset-pass-assembly:
> zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.samigo:samigo-
> assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.scheduler:
> scheduler-assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> search:search-assembly:zip:tomcat-overlay:1.4.0 (compile), org.sakaiproject.
> shortenedurl:shortenedurl-assembly:zip:tomcat-overlay:1.1.0 (compile), org.
> sakaiproject.site:sakai-site-assembly:zip:tomcat-overlay:2.9.0 (compile),
> org.sakaiproject.sitestats:sitestats-assembly:zip:tomcat-overlay:2.3.0
> (compile), org.sakaiproject.taggable:sakai-taggable-assembly:zip:tomcat-
> overlay:2.9.0 (compile), org.sakaiproject.velocity:sakai-velocity
> -assembly:zip:tomcat-overlay:2.9.0 (compile), org.sakaiproject.
> webservices:webservices-assembly:zip:tomcat-overlay:1.1.0 (compile),
> junit:junit:jar:3.8.1 (test)]
> at org.sonatype.aether.impl.internal.
> DefaultDependencyCollector.
> collectDependencies(DefaultDependencyCollector.java:258)
> at org.sonatype.aether.impl.internal.DefaultRepositorySystem.
> collectDependencies(DefaultRepositorySystem.java:308)
> at org.apache.maven.project.DefaultProjectDependenciesResolver
> .resolve(DefaultProjectDependenciesResolver.java:150)
> ... 23 more
> Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException:
> Failed to read artifact descriptor for org.sakaiproject.message:sakai-
> message-assembly:zip:tomcat-overlay:2.9.0
> at org.apache.maven.repository.internal.
> DefaultArtifactDescriptorReader.
> loadPom(DefaultArtifactDescriptorReader.java:296)
> at org.apache.maven.repository.internal.
> DefaultArtifactDescriptorReader.
> readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
> at org.sonatype.aether.impl.internal.DefaultDependencyCollector.
> process(DefaultDependencyCollector.java:412)
> at org.sonatype.aether.impl.internal.DefaultDependencyCollector.
> collectDependencies(DefaultDependencyCollector.java:240)
> ... 25 more
> Caused by: org.sonatype.aether.resolution.
> ArtifactResolutionException:
> Could not transfer artifact org.sakaiproject.message:sakai-message-assembly:
> pom:2.9.0 from/to sakai-maven (http://source.sakaiproject.org/maven2):
> Connection reset
> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.
> resolve(DefaultArtifactResolver.java:538)
> at org.sonatype.aether.impl.internal.DefaultArtifactResolver.
> resolveArtifacts(DefaultArtifactResolver.java:216)
> at org.sonatype.aether.impl.internal.DefaultArtifactResolver
> .resolveArtifact(DefaultArtifactResolver.java:193)
> at org.apache.maven.repository.internal.
> DefaultArtifactDescriptorReader
> .loadPom(DefaultArtifactDescriptorReader.java:281)
> ... 28 more
> Caused by: org.sonatype.aether.transfer.ArtifactTransferException:
> Could not transfer artifact org.sakaiproject.message:sakai-message-assembly
> :pom:2.9.0 from/to sakai-maven (http://source.sakaiproject.org/maven2):
> Connection reset
> at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4
> .wrap(WagonRepositoryConnector.java:951)
> at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4
> .wrap(WagonRepositoryConnector.java:941)
> at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$
> GetTask.run(WagonRepositoryConnector.java:669)
> at org.sonatype.aether.util.concurrency.
> RunnableErrorForwarder$1.
> run(RunnableErrorForwarder.java:60)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.
> runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.
> run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.maven.wagon.TransferFailedException:
> Connection reset
> at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon
> .fillInputData(AbstractHttpClientWagon.java:799)
> at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
> at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
> at org.sonatype.aether.connector.wagon.
> WagonRepositoryConnector$GetTask.run
> (WagonRepositoryConnector.java:601)
> ... 4 more
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:168)
> at org.apache.maven.wagon.providers.http.httpclient.impl.io.
> AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
> at org.apache.maven.wagon.providers.http.httpclient.impl
> .io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
> at org.apache.maven.wagon.providers.http.httpclient.impl
> .io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
> at org.apache.maven.wagon.providers.http.httpclient.impl
> .conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
> at org.apache.maven.wagon.providers.http.httpclient.impl.io.
> AbstractMessageParser.parse(AbstractMessageParser.java:252)
> at org.apache.maven.wagon.providers.http.httpclient.impl
> .AbstractHttpClientConnection.receiveResponseHeader
> (AbstractHttpClientConnection.java:281)
> at org.apache.maven.wagon.providers.http.httpclient.impl
> .conn.DefaultClientConnection.receiveResponseHeader
> (DefaultClientConnection.java:247)
> at org.apache.maven.wagon.providers.http.httpclient.impl.conn
> .AbstractClientConnAdapter.receiveResponseHeader
> (AbstractClientConnAdapter.java:219)
> at org.apache.maven.wagon.providers.http.httpclient.protocol
> .HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
> at org.apache.maven.wagon.providers.http.httpclient.protocol
> .HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
> at org.apache.maven.wagon.providers.http.httpclient.impl.client
> .DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645)
> at org.apache.maven.wagon.providers.http.httpclient.impl.client
> .DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
> at org.apache.maven.wagon.providers.http.httpclient.impl.client
> .AbstractHttpClient.execute(AbstractHttpClient.java:820)
> at org.apache.maven.wagon.providers.http.httpclient.impl.client
> .AbstractHttpClient.execute(AbstractHttpClient.java:754)
> at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon
> .execute(AbstractHttpClientWagon.java:674)
> at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon
> .fillInputData(AbstractHttpClientWagon.java:793)
> ... 8 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :core-deploy
> -bash-3.2$
>
>
>
>
> ------------------------------
>
> Message: 28
> Date: Wed, 13 Mar 2013 11:52:23 -0400
> From: Earle Nietzel <earle.nietzel at gmail.com>
> Subject: Re: [Building Sakai] Spring 3.2 and Hibernate 3.6 upgrades
> (KNL-515 / KNL-517)
> To: Steve Swinsburg <steve.swinsburg at gmail.com>
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <CAD3fRztLwTpofAkqJX=PY115mHi8-g5syKeMLJieHhfL94Fi1Q at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Nice job, this was definitely needed.
>
> Earle
>
>
> On Tue, Mar 12, 2013 at 4:12 AM, Steve Swinsburg
> <steve.swinsburg at gmail.com>wrote:
>
>> Excellent work all, looking forward to using it!
>>
>> Cheers
>> Steve
>>
>> Gesendent von meinem iPhone
>>
>> On 12/03/2013, at 8:20, Noah Botimer <botimer at umich.edu> wrote:
>>
>> Hello all,
>>
>> I'm pleased to note the completion of upgrades to Spring 3.2.1.RELEASE and
>> Hibernate 3.6.10.Final, and that preliminary testing has gone very well.
>>
>> But don't panic! This isn't in trunk yet; just standing by to be merged.
>>
>>
>> There are lots of details on the tickets [1][2], but the most important
>> thing is that there is very good backward compatibility. Most of the things
>> you would have done in code are unchanged.
>>
>> Two obvious exceptions (config, not really code) to these are the
>> dependencies declared (both libraries are now modular) and the universal
>> use of the "materialized_clob" datatype for long text data (a consistency
>> improvement, which maps a Java String to a CLOB / TEXT field, as was
>> previously accomplished with string types and length limits). All known
>> changes have been applied to all of the core, so you shouldn't have to
>> worry too much. All tests pass nicely. Contrib maintainers: it's pretty
>> straightforward for any given tool.
>>
>> There will be some more documentation about the specifics (say, some of
>> the constant or cache region changes), but this is ready for broad testing
>> now. Because nearly every module is touched, this upgrade is not in a set
>> of Subversion branches (way too much work). I am maintaining them on GitHub
>> and keeping a branch synchronized with trunk:
>>
>> https://github.com/botimer/sakai-cle/tree/spring-32
>>
>> I've done testing on MySQL and Oracle. Others (Sam, Aaron, Zach, Chris)
>> have been testing as well, and we have found no standing regressions. So, I
>> will put it to the TCC to think about the right time to apply these changes
>> to trunk. I am deliberately sharing this now, after 2.9.1 has settled,
>> since I think this is about the right time.
>>
>> I should also note that this was a big chunk of work, graciously sponsored
>> by Unicon.
>>
>> Comments, test results, and pull requests are welcome.
>>
>> Thanks,
>> -Noah
>>
>> [1] - https://jira.sakaiproject.org/browse/KNL-515
>> [2] - https://jira.sakaiproject.org/browse/KNL-517
>>
>> _______________________________________________
>>
>> 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/20130313/78488013/attachment-0001.html
>
> ------------------------------
>
> Message: 29
> Date: Wed, 13 Mar 2013 11:03:17 -0500
> From: Gregory Guthrie <guthrie at mum.edu>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: John Bush <john.bush at rsmart.com>, Steve Swinsburg
> <steve.swinsburg at gmail.com>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <08EF9DA445C4B5439C4733E1F35705BA024749F762CD at MAIL.cs.mum.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> This sounds good! One question is if this is automatic SCAYT - (spell check as you type) which I think is pretty much the current standard, or an explicit manual batch check of a document when done?
>
> I like the Moodle description: "should be familiar to anyone who uses a word processor"...
>
> From: John Bush [mailto:john.bush at rsmart.com]
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
>
> The google one doesn't require a third party install or any costs. The library is Apache 2.0, and the only risk is that the google service is unavailable (in which case you just won't get any corrections, which seems like low risk considering the use case, and the provider is google). Another advantage is that it has decent i18n support out of the gate, its capturing the sakai locale from ResourceLoader and sending that over to the google call, and Kevin already built it, so its ready to go.
>
> On Wed, Mar 13, 2013 at 12:45 PM, Gregory Guthrie <guthrie at mum.edu<mailto:guthrie at mum.edu>> wrote:
>
> http://docs.moodle.org/23/en/Text_editor
>
> The text editor (sometimes referred to as the 'HTML editor' or even 'TinyMCE') has many icons to assist the user in entering content. Many of these icons and functions should be familiar to anyone who uses a word processor. Some examples of where you will see the text editor include: Editing Section headings, description of an activity, writing an answer to a quiz question or editing the content of many blocks.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/c0491d69/attachment-0001.html
>
> ------------------------------
>
> Message: 30
> Date: Wed, 13 Mar 2013 12:06:05 -0400 (EDT)
> From: ottenhoff at longsight.com
> Subject: [Building Sakai] CLE Team Call, Thursday, 2013-03-14,
> 10:00EST (15:00GMT)
> To: cle-release-team at collab.sakaiproject.org
> Cc: sakai-qa at collab.sakaiproject.org,
> sakai-dev at collab.sakaiproject.org
> Message-ID: <20130313160605.37635128537 at support.longsight.com>
> Content-Type: text/plain; charset="us-ascii"
>
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/e01636dd/attachment-0001.html
>
> ------------------------------
>
> Message: 31
> Date: Wed, 13 Mar 2013 09:30:38 -0700
> From: Kevin Takacs <ktakacs at rsmart.com>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Gregory Guthrie <guthrie at mum.edu>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>, John Bush <john.bush at rsmart.com>
> Message-ID:
> <CAAr3_5PuinNbKJ2TX42HYgXAFXPMvYd_7s49nWQcG+1QbD8iSw at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> The google spell checker does a batch check of the entire document.
>
> On Wed, Mar 13, 2013 at 9:03 AM, Gregory Guthrie <guthrie at mum.edu> wrote:
>
>> This sounds good! One question is if this is automatic SCAYT ? (spell
>> check as you type) which I think is pretty much the current standard, or an
>> explicit manual batch check of a document when done?****
>>
>> ** **
>>
>> I like the Moodle description: ?should be familiar to anyone who uses a
>> word processor??****
>>
>> ** **
>>
>> *From:* John Bush [mailto:john.bush at rsmart.com]
>> *Subject:* Re: [Building Sakai] CKEditor & Spelling correction.****
>>
>> ** **
>>
>> The google one doesn't require a third party install or any costs. The
>> library is Apache 2.0, and the only risk is that the google service is
>> unavailable (in which case you just won't get any corrections, which seems
>> like low risk considering the use case, and the provider is google).
>> Another advantage is that it has decent i18n support out of the gate, its
>> capturing the sakai locale from ResourceLoader and sending that over to the
>> google call, and Kevin already built it, so its ready to go.****
>>
>> ** **
>>
>> On Wed, Mar 13, 2013 at 12:45 PM, Gregory Guthrie <guthrie at mum.edu> wrote:
>> ****
>>
>> http://docs.moodle.org/23/en/Text_editor ****
>>
>> The text editor (sometimes referred to as the 'HTML editor' or even
>> 'TinyMCE') has many icons to assist the user in entering content. Many of
>> these icons and functions should be familiar to anyone who uses a word
>> processor. Some examples of where you will see the text editor include:
>> Editing Section headings, description of an activity, writing an answer to
>> a quiz question or editing the content of many blocks.****
>>
>> _______________________________________________
>> 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"
>>
>
>
>
> --
> Kevin Takacs
> *r**Smart* | Sakai Software Engineer
> ktakacs at rsmart.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/e9d9a89c/attachment-0001.html
>
> ------------------------------
>
> Message: 32
> Date: Wed, 13 Mar 2013 16:33:26 +0000 (UTC)
> From: Fatemeh Asl <aa2821 at nyumc.org>
> Subject: [Building Sakai] mvn repository on source.sakaiproject.org
> are not availabale
> To: sakai-dev at collab.sakaiproject.org
> Message-ID: <loom.20130313T173217-726 at post.gmane.org>
> Content-Type: text/plain; charset=us-ascii
>
>
> Hi,
>
> I can't open
> http://source.sakaiproject.org/maven2/org/sakaiproject/message/sakai-message-assembly/
> . Any idea please?
>
> Thanks
> Fatemeh
>
>
>
> ------------------------------
>
> Message: 33
> Date: Wed, 13 Mar 2013 11:57:45 -0500
> From: Omer A Piperdi <omer at rice.edu>
> Subject: [Building Sakai] Samigo Question
> To: "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID: <5140B009.4010704 at rice.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> One of our instructor edited a published assessment to change the due
> date.. Since she made the changes, published assessment changed into
> Inactive status on web. And the link to check submitted assessment is
> NOT shown on instructor screen. However, students can still see their
> submitted assessment and can still take it..
>
> I am wondering this is because the status being inactive. Where is the
> active/inactive information for a test quizzes stored in the database?
> The status is 1 in sam_publishedassessment_t table.
>
> Thanks
> Omer
>
>
>
> ------------------------------
>
> Message: 34
> Date: Wed, 13 Mar 2013 12:29:38 -0500
> From: Gregory Guthrie <guthrie at mum.edu>
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> To: Kevin Takacs <ktakacs at rsmart.com>
> Cc: "sakai-user at collab.sakaiproject.org"
> <sakai-user at collab.sakaiproject.org>,
> "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>, John Bush <john.bush at rsmart.com>
> Message-ID:
> <08EF9DA445C4B5439C4733E1F35705BA024749F762D7 at MAIL.cs.mum.edu>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Then I'm not sure this adds much over the "Speller Pages" option for CKEditor, or the fairly cheap current option from WebSpellChecker.net ($250/year). Our goal would be SCAYT which is what I think most users will be expecting (and prefer).
>
> I wasn't sure how to read the CKEditor page description of their "Native Spell Checker" (http://docs.ckeditor.com/#!/guide/dev_spellcheck), but might that just defer spelling to the browser, which I think most do a good job on already?
>
> ---------------------------------
> - Kevin Takacs
> - rSmart | Sakai Software Engineer
> The google spell checker does a batch check of the entire document.
> On Wed, Mar 13, 2013 at 9:03 AM, Gregory Guthrie <guthrie at mum.edu> wrote:
>> This sounds good! One question is if this is automatic SCAYT - (spell check as you type) which I think is pretty much the current standard, or an explicit manual batch check of a document when done?
> ?
> I like the Moodle description: "should be familiar to anyone who uses a word processor".
> ?
> From: John Bush [mailto:john.bush at rsmart.com]
> Subject: Re: [Building Sakai] CKEditor & Spelling correction.
> ?
> The google one doesn't require a third party install or any costs. ?
>
>
>
> ------------------------------
>
> Message: 35
> Date: Wed, 13 Mar 2013 17:56:56 +0000
> From: "Kaufmann,Melody-Ann J" <safire at ufl.edu>
> Subject: [Building Sakai] Samigo time assesment issue in Sakai 2.9
> To: "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <6F7E28669B715F4086202393BDBF6D2C63A77A76 at UFEXCH-MBXN03.ad.ufl.edu>
> Content-Type: text/plain; charset="us-ascii"
>
> Greetings All,
>
> Currently I am seeing an issue exhibited with Samigo pertaining to timed assessments lagging out upon clicking 'submit' or after the first question on clicking 'next'.
>
> Contributing information: The implementation currently uses sakai 2.9 with an Oracle back end.
>
> Steps to replicate:
> 1). Timed assessment is started by student
> 2) student answers first question and clicks next
> 3) Student answers second question and clicks next
> 4) lag occurs until student either runs out of time or leaves the assessment
> 5) if the student leaves the assessment, they return to the assessment on the 'next' item. The student will continue to experience lagging out at each click of 'next' or 'submit' in these instances
>
> I have found that this issue is only occurring in assessments which are timed. All other assessments regardless of questions type composition behave as expected on non-timed assessments.
>
> I have attached a copy of the catalina.out logs which cover the period of time from starting the assessment until its time out. Any sugesstions or assistance in this matter would be greatly appreciated
>
> Thanks,
> MJ
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/ab5f0d3c/attachment-0001.html
> -------------- next part --------------
> An embedded and charset-unspecified text was scrubbed...
> Name: assessment_logs.txt
> Url: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130313/ab5f0d3c/attachment-0001.txt
>
> ------------------------------
>
> Message: 36
> Date: Wed, 13 Mar 2013 11:49:38 -0700 (PDT)
> From: SamuelGJ <samuelgutierrezjimenez at gmail.com>
> Subject: Re: [Building Sakai] Sakai 2.9.1 and tomcat 7
> To: sakai-dev at collab.sakaiproject.org
> Message-ID: <1363200578833-7587151.post at n2.nabble.com>
> Content-Type: text/plain; charset=UTF-8
>
> I'm using the version 2.9.1 Sakai from:
>
> *https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.1/*
>
> For now I have not had any Problem with this version.
>
> The line: /Could not transfer artifact
> org.sakaiproject.message:sakai-message-assembly:
> pom:2.9.0 from/to sakai-maven (http://source.sakaiproject.org//*maven2*)
>
> Tell me...What version of Maven, Tomcat and Subversion have you ?
>
> It?s necessary install the *maven version 3*.
>
> I think that following the instructions on the link you spent in the
> previous post shouldn't cause you such errors.
>
> Regards, Samuel.
>
>
>
>
> --
> View this message in context: http://sakai-project-mail-list-archives.1343168.n2.nabble.com/Building-Sakai-Sakai-2-9-1-and-tomcat-7-tp7587036p7587151.html
> Sent from the DG: Development / Buidling Sakai (sakai-dev at collab.sakaiproject.org) mailing list archive at Nabble.com.
>
>
> ------------------------------
>
> Message: 37
> Date: Wed, 13 Mar 2013 18:54:51 +0000
> From: David Horwitz <david.horwitz at uct.ac.za>
> Subject: Re: [Building Sakai] Sakai 2.9.1 and tomcat 7
> To: SamuelGJ <samuelgutierrezjimenez at gmail.com>
> Cc: "sakai-dev at collab.sakaiproject.org"
> <sakai-dev at collab.sakaiproject.org>
> Message-ID:
> <B4A6423C879F864A9D42EF2FBA906D69F7D8F5 at SRVWINEXC003.wf.uct.ac.za>
> Content-Type: text/plain; charset=UTF-8
>
> Also if you are behind a proxy you need to configure maven to use it.
>
> Regards
>
> David
>
> On Wed, 2013-03-13 at 11:49 -0700, SamuelGJ wrote:
>> I'm using the version 2.9.1 Sakai from:
>>
>> *https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.1/*
>>
>> For now I have not had any Problem with this version.
>>
>> The line: /Could not transfer artifact
>> org.sakaiproject.message:sakai-message-assembly:
>> pom:2.9.0 from/to sakai-maven (http://source.sakaiproject.org//*maven2*)
>>
>> Tell me...What version of Maven, Tomcat and Subversion have you ?
>>
>> It?s necessary install the *maven version 3*.
>>
>> I think that following the instructions on the link you spent in the
>> previous post shouldn't cause you such errors.
>>
>> Regards, Samuel.
>>
>>
>>
>>
>> --
>> View this message in context: http://sakai-project-mail-list-archives.1343168.n2.nabble.com/Building-Sakai-Sakai-2-9-1-and-tomcat-7-tp7587036p7587151.html
>> Sent from the DG: Development / Buidling Sakai (sakai-dev at collab.sakaiproject.org) mailing list archive at Nabble.com.
>> _______________________________________________
>> 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"
>
> ________________________________
> UNIVERSITY OF CAPE TOWN
>
> This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.
>
> ------------------------------
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
>
> End of sakai-dev Digest, Vol 49, Issue 13
> *****************************************
More information about the sakai-dev
mailing list