[sakai2-tcc] Depreciation of the Profile tool

[Steve Swinsburg]

I'm awake but more importantly I finally have a net connection (moved house, no 3g coverage).

I haven't tested this approach yet but it should work. This would mean that the Profile2 assembly deploys an additional jar to shared/lib, that being the classic profile API jar. We can then drop the profile classic assembly altogether since it is an indie. The tool, help and components would then be dropped also.

The Roster work that Lancs were doing was going to remove this dependency altogether as the integration is EntityBroker based, but its not there yet. And I don't think anyone has the resources to adjust the current Roster to make it EB based.

What are your thoughts?

cheers,
Steve


On 11/12/2010, at 1:12 AM, Berg, Alan wrote:

> Hi all ,
> 
> According to the TCC planning, the profile tool is to be depreciated.  Currently the profile2 tool needs some residue api interfaces.  When he is awake, Steve Swinsberg can comment further, but following Steve's suggestion
> Is it OK to  fix the profile assembly to only deploy the API jar? 
> 
> I consider this a sensible approach as:
> 
> 1) It limits the amount of work involved for the developer and the testers
> 2) Removes any bloat.
> 3) Keeps to the spirit of the TCC plan.
> 
> Alan
> 
> Alan Berg
> QA Director - The Sakai Foundation
> 
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
> 
> http://home.uva.nl/a.m.berg
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20101213/0085b40d/attachment.html