[sakai2-tcc] More Indie Thinking on Profile2 / Profile

[Steve Swinsburg]

Can you use the Entity Providers to get the data from Profile2 or do you explicitly need the Java API's? 

I'm thinking that splitting application up will make it harder to perform releases as if any backend work happens in Profile2 (as it almost always does between releases), then both Common and the Profile2 tool need to be released and makes it harder for people to upgrade.  It will also break the easy upgrade path that the indie releases provide - update the version in the pom, deploy, done.

Common has historically contained complete services and hasn't left tools (that are being worked on) dangling.

Interesting discussion though if others have any input.

cheers,
Steve




On 31/08/2010, at 3:46 AM, csev wrote:

> As I think about the work I am planning to do for 2.9, I will be building services that depend heavily on Profile2 services and those services will be used by lots of other tools.
> 
> It would work best if both the profile2 service were placed in common as well as my new service - then folks working in common would (a) be continuously checking each other's work and catching to see if things break and (b) dependencies would work nicely.    
> 
> I would like to see common the place we put common services that lots of things depend on rather than making a lot of multi-layer indie dependency chains.
> 
> /Chuck
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3689 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100831/b7686155/attachment.bin