[Building Sakai] Deprecation Notice: kernel static covers

[csev]

-1 

Covers are not harmful and the transition from K1 to K2 is a complete rewrite and of course K2 will never have covers. If K1 to K2 were some kind of "upgrade" - we should deprecate all of K1.

I personally think that excessive use of Spring when not needed is *bad practice*.   I am happy to switch to the more factory-like locator pattern - but switching to Spring injection is not a step forward IMHO in terms of code cleanliness and maintainability.  And is it not the case that K2 a completely different service model?

Don't even deprecate these.  We don't want to have so many deprecation warnings that we start to ignore them in general or turn them off in compiles - this way when there is something that *really* needs attention because a third-party jar is changing will get missed in the sea of superfluous deprecation warnings.

/Chuck

On Mar 17, 2010, at 4:04 AM, David Horwitz wrote:

> Deprecation Notice: In the next scheduled release in the 1.1 kernel series (1.1.2) all the Static covers of kernel services will be marked as deprecated. Developers are urged to review their code and replace the use of static covers with spring injection or lookup from the component manager in line with stated Sakai best practices [http://confluence.sakaiproject.org/display/SAKDEV/Best+Practices+for+Kernel+code#BestPracticesforKernelcode-Nousageofstaticcovers]. The covers are scheduled for removal in Kernel 2.0.0
> 
> Regards
> 
> David
> 
> _______________________________________________
> 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"
> 
>