[sakai2-tcc] sakai-2.8.0-a01 update: Hybrid

Anthony Whyte arwhyte at umich.edu
Tue Sep 21 12:51:44 PDT 2010


I've worked with Lance over the last hour to create a hybrid-assembly module, create a hudson job to automate hybrid snapshot deployments, deploy hybrid-1.0-SNAPSHOT artifacts to the Maven snapshot repo and then add the hybrid assembly dependency to the trunk core-deploy pom.  I've tested all locally and hybrid is downloaded, installed and deployed to Tomcat without issue.  I've asked Lance to provide me with any default hybrid properties that should be added to default.sakai.properties (forthcoming)

In short, hybrid is now deployed by trunk and will be included in the sakai-2.8.0-a01 tag.

Seth tells me inclusion in 2.8.0 requires a formal vote.  Should the vote go against hybrid it will be trivial to remove references to it from the master and core-deploy poms.

http://jira.sakaiproject.org/browse/SAK-19185

Cheers,

Anth


Begin forwarded message:

> From: "Speelmon, Lance Day" <lance at indiana.edu>
> Date: September 21, 2010 11:52:31 AM EDT
> To: David Horwitz <dhorwitz at gmail.com>
> Cc: "May, Megan Marie" <mmmay at indiana.edu>, "<mt at collab.sakaiproject.org>" <mt at collab.sakaiproject.org>
> Subject: Re: [maint] Fwd: [Management] [Building Sakai] Sakai 2.8 Release Activity Schedule
> 
> 1) I have made all of the changes suggested by David - thanks!
> 2) As part of my test plans, I have created a ruby-based integration test of the hybrid REST endpoints:
> http://github.com/sakaiproject/nakamura/commit/8fd165b6ffa54753cce8526a4d5f2f7fa2a555bf
> 3) I have some simple instructions on testing the login and providers components.  These test plans should be done in about a day.
> 
> Am I ready for a merge?  :)  Thanks!  L
> 
> 
> Lance Speelmon
> Scholarly Technologist
> 
> On Sep 19, 2010, at 7:25 AM, David Horwitz wrote:
> 
>> Hi Lance,
>> 
>>> 3) hybrid: http://github.com/sakaiproject/nakamura/tree/master/hybrid/
>>> 3.1) Indie release - needs a maven maven's help to release an artifact into
>>> the sakai repo.
>>> 3.2) Provides two REST endpoints for Sakai 2. Both servlets are filtered by
>>> TrustedLoginFilter (i.e. x-sakai-token) and execute in the context of the
>>> current user.
>>>  A) /sakai-hybrid/sites
>>>     200 OK
>>>  B) /sakai-hybrid/site?siteId=1234 OR
>>> /sakai-hybrid/site?siteId=1234?writeEvent=true
>>>     200 OK; 400 bad siteId passed; 403 permission exception; 404 siteId not
>>> found
>> 
>> I pushed some pom updates to my github
>> (http://github.com/axxter99/open-experiments/commit/df2b73d9034fb32376ef7bcf3e2bd26bf8a86516)
>> - not sure which is your repo :-) Could you pull and review. Overview
>> of changes:
>> 
>> 1) Changed parent to sakai standard tool
>> 2) changed groupId to org.sakaiproject.hybrid (to help preserve repo
>> manigability)
>> 2) add distribution management to the pom
>> 3) added license info to the pom
>> 4) added developer info to the pom (check I got it righ :-)
>> 5) added scm info
>> 
>> The last definatly we want to check (I've never done this for git) It
>> points to central - we may want to do the intial release against
>> another repo first.
>> 
>> Another note is that I see 2 snapshot dependencies: nakamura-utils &
>> portal-utils before we can release we need release versions of these.
>> For nakamura utils I would recommend that if 0.8 is compatible we use
>> a version range that starts there. For portal I think the time has
>> come to indify portal :-)
>> 
>> D
>> 
>> 
>>> Thanks! Lance
>>> Lance Speelmon
>>> Scholarly Technologist
>>> Begin forwarded message:
>>> 
>>> I have some Sakai 2/3 Hybrid changes I would like to land for Sakai 2.8:
>>> 
>>> 1) login: http://jira.sakaiproject.org/browse/SAK-17223
>>> 
>>> 2) providers: http://jira.sakaiproject.org/browse/SAK-17222
>>> 
>>> I would appreciate additional eyes before merging the code.  A patch is
>>> attached to each issue for easy review.
>>> 
>>> We might also consider having 2.8 bind to a released version
>>> of:http://github.com/sakaiproject/nakamura/tree/master/hybrid/
>>> 
>>> This module provides a couple of REST endpoints for the Sakai 3 portal (i.e.
>>> list of sites for current user, and list of tools for a given site). I will
>>> likely need to defer to the maven mavens on this issue.
>>> 
>>> So we should probably start a discussion of next steps for hybrid inclusion.
>>> Thanks!  L
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> mt mailing list
>>> mt at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/mt
>>> 
>>> 
> 
> _______________________________________________
> mt mailing list
> mt at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/mt
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100921/b77846f3/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100921/b77846f3/attachment.bin 


More information about the sakai2-tcc mailing list