[Building Sakai] [sakai-pmc] Removing standalone modes for sections/gradebook

[prabhu]

Hi,
      Thanks for all for supporting me by replying for all my queries. Now
I am trying to use CAS as SSO along with SAKAI. I have installed CAS 3.4.7
and sakai 2.9.1. I have made the changes to sakai to use CAS as login
module. The issue I have is CAS ticket not being accepted by the sakai. I
know the issue could be because I am using the SSL. Please help me to
import the SSL certificate into the JVM store to avoid the issue.


On Fri, Nov 8, 2013 at 4:07 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Inform people it will be removed in x release. Remove it. People can patch
> it back in if they really need it. We should not hold up progress for
> issues that are easily resolved via minor local modifications.
>
> There will always be people that don't get the message and discover it
> come upgrade time, ie the vast number of people that had no idea about the
> common/edu services refactor that posted months/years after it was
> implemented.
>
> Forget the survey, let's get it done.
>
> Cheers,
> Steve
>
> Sent from my iPad
>
> On 9 Nov 2013, at 1:40, Noah Botimer <botimer at umich.edu> wrote:
>
> I am persuaded that a (classical) survey would be ineffective. Perhaps a
> better phrasing is an announcement of intent and a defined window to pipe
> up.
>
> I guess this dovetails with the "informed community" thread. I have not
> yet seen evidence that any work of substance or usage on the standalone
> pieces has happened in over five years, so I read this as a low risk item,
> the gradebook test suite caveat acknowledged.
>
> Thanks,
> -Noah
>
> On Nov 8, 2013, at 9:06 AM, Matthew Jones wrote:
>
> Yea, that's kind of why I anyone could continue using the 2.9 and earlier
> Gradebook which is pretty solid. The documentation that exists mentions
> really old versions of tomcat and Sakai so I imagine if anyone is running
> it, that they are probably still running Sakai 2.4 or 2.5. We've just be
> carrying along all this old code and having random problems when it doesn't
> compile and it's unable to be tested. Though I wasn't 100% sure. I expected
> that if Berkeley or IU didn't say anything then it was probably good to
> pull out.
>
> Though in the gradebook case, nearly all of the test cases are in the
> standalone app. I would be nice to preserve the ones that can still work
> here. So I might not do a full cleanup, as much as I did with sections
> anyway. Or maybe these tests need to be moved around a little. Haven't
> tried to do anything with gradebook yet.
>
>
> On Fri, Nov 8, 2013 at 8:59 AM, Sam Ottenhoff <ottenhoff at longsight.com>wrote:
>
>> I imagine there are 1 or 2 people in this community who have experimented
>> or used the standalone versions of these tools, and a survey would be a
>> pretty inefficient way of finding them.
>>
>>
>> On Thu, Nov 7, 2013 at 2:47 PM, Matthew Jones <matthew at longsight.com>wrote:
>>
>>> 2 issues are considered blockers for the release of Sakai 10
>>>
>>> https://jira.sakaiproject.org/browse/SAK-23918
>>> https://jira.sakaiproject.org/browse/SAK-23917
>>>
>>> These are both related to sections and gradebook depending on impl's
>>> that have been moved into edu-services. The cross between edu-services and
>>> these tools isn't completely clean and much of it is continued support for
>>> the a feature called "standalone". I've never ran this feature, only read
>>> about it in some of the old docs. Nobody on the release call was running
>>> these tools "standalone". The documentation on this mode is over 7 years
>>> old and it seemed to imply you did need some parts of Sakai to get it to
>>> run. The release team call suggestion is to just remove standalone
>>> capability from these tools in Sakai 10. This would simplify the code in
>>> these tools and remove these dependencies.
>>>
>>> However, before I committed this I wanted to a check to verify nobody
>>> outside of the call was using this mode and would miss it. If so would they
>>> consider supporting the work to fix this dependency problem and test this
>>> mode. The alternative I could think of would probably be profiles specific
>>> for the standalone mode which would only compile these standalone classes
>>> and include these dependencies when specifically enabled.
>>>
>>> Obviously they would remain in versions of Sakai 2.9 and earlier.
>>>
>>> I plan to commit the removal of these next week if there is no
>>> dissenting opinion. I've done this locally for sections and it seems to
>>> work fine, gradebook looks like a little more involved.
>>>
>>> Thanks!
>>>
>>> _______________________________________________
>>> sakai-pmc mailing list
>>> sakai-pmc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>>
>>>
>>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
> _______________________________________________
> 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"
>



-- 








*-----------------------------------------------------------------------------------------------------------------------------------------------Regards:Prabhu
Janakaraj,Consultant Linux and Networking - Training and Deployment, Skype:
prabhu.j4Handphone: 091 9790 382 999*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131108/38c6cd4a/attachment.html