[Building Sakai] MT deprecation recommendationsfor 2.7

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Tue Mar 23 03:01:52 PDT 2010


+1

David Horwitz a écrit :
> +1
> 
> On 03/22/2010 03:23 PM, David Haines wrote:
>> Yes.  Let's retain, depreciate, and move on.
>>
>> - Dave
>>
>> David Haines
>> CTools Developer
>> Digital Media Commons
>> University of Michigan 
>> dlhaines at umich.edu <mailto:dlhaines at umich.edu>
>>
>>
>>
>>
>> On Mar 22, 2010, at 8:45 AM, Stephen Marquard wrote:
>>
>>> I agree with Aaron's last para (deprecate, never remove, remove use 
>>> from core code), and hope we can bring this thread to a conclusion soon.
>>>
>>> Cheers
>>> Stephen
>>>
>>>>>> Aaron Zeckoski <azeckoski at unicon.net 
>>>>>> <mailto:azeckoski at unicon.net>> 3/22/2010 2:20 PM >>>
>>> I feel like it is worth mentioning here that in the Sakai 3 kernel you
>>> will only be able to access services via OSGi mechanisms which are
>>> similar to spring but use either xml or annotations (currently
>>> anyway). There will be no spring/spring xml, component manager, or
>>> static covers so while it may be ok to leave this stuff in Sakai 2 it
>>> is not going to help anyone get used to the way things are going to
>>> work in the future.
>>>
>>> I am still on the side of leaving the covers in as a convenience to
>>> developers who have used them, deprecating them and removing their use
>>> from core code.
>>>
>>> -AZ


More information about the sakai-dev mailing list