[Building Sakai] MT deprecation recommendationsfor 2.7

[Mark Norton]

No, let's retain, document the recommended practice, NOT deprecate it, 
and move on.

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
>>
>>
>>
>>
>>
>> ______________________________________________________________________________________________ 
>>
>>
>> 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 4500. 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 
>> <mailto: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"