[Building Sakai] Merge request: Kernel API change (KNL-601)

[David Horwitz]

  My concern then is that its a minimum 18 months before we can fix the 
provisioning code - that seems from my testing very broken in the cases 
where CM reports groups that are empty.

D

On 01/14/2011 02:46 PM, Jean-Francois Leveque wrote:
> +1 for K1.3 (S2.9)
> -1 for K1.2 (S2.8) or earlier (API change) : seen merge requested in 
> issue
>
> This will force those who want a fix quickly to build a custom kernel, 
> but I think we don't want to force (at this time of 2.8 release 
> management) custom group providers owners to update their 
> implementations.
>
> J-F
>
> David Horwitz a écrit :
>> Hi All,
>>
>> This refers to https://jira.sakaiproject.org/browse/KNL-601 and the
>> related provider updates in 
>> https://jira.sakaiproject.org/browse/SAK-19821
>>
>> KNL-601 adds a new method the the groupProvider to check that a group
>> exists. Prior to this change there was no way via the interfaces to
>> distinguish between an empty group and a invalid groupId. At UCT this is
>> currently giving us problems as lecturers try to setup courses ahead of
>> the start of term next month.
>>
>> Impact of merging: All deployers who have custom group providers will
>> need to add 1 method to their group provider implementation.
>>
>> Any objections?
>>
>> D