[cle-release-team] Roster2: adding to the experimental build

Mon Oct 28 16:23:58 PDT 2013

I've got the experimental build fixed locally and running roster2.  The experimental profile was out of date, referencing both pure-poms and the hybrid modules--I've removed both and added roster2.  Trunk commits are recorded in RSTR-66. [1]

Trunk checkouts now include roster2 and those who wish to evaluate it as a candidate for the next trunk-based Sakai release should activate the "experimental" profile:

mvn -Pexperimental clean install sakai:deploy 

I will follow up with a proposal for pulling roster2 into core once the Nightly2 build is confirmed and Steve/Adrian check that roster2 is functioning properly.

Cheers,

Anth

[1] https://jira.sakaiproject.org/browse/RSTR-66

anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu | 517-980-0228

On Oct 24, 2013, at 9:51 AM, Thomas, Gregory J wrote:

> Yeah, the experimental nightly server was broken for a long time since about September 12th due to the changes that happened in https://jira.sakaiproject.org/browse/SAK-23907
> 
> So, in an effort to the server at least functional again, some of indie modules that experimental pulls in were commented out from the main pom.xml to get a full compile.  Everything, except Roster2 has been fixed and readded.  As soon as Roster2 has been addressed, it's just a matter of uncommenting it out from https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-experimental/pom.xml and it'll be good to go again.  If it's good to go already, then we can go ahead and do the change and not wait for Friday.
> 
> Greg
> 
> From: Adrian Fish <adrian.r.fish at gmail.com>
> Date: Thursday, October 24, 2013 2:19 AM
> To: Steve Swinsburg <steve.swinsburg at gmail.com>
> Cc: "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>
> Subject: Re: [cle-release-team] Roster2: adding to the experimental build
> 
> I am plagued by Adams. We have an Adam Fish here at Lancaster. I keep getting his emails and even the odd, curious 'phone call. Yesterday, some guy rang me and said, out of the blue and in a German accent, "When can I pick up that video camera?". I said "Err, video camera?". He thought he'd rung Adam, lol.
> 
> It was just the build order then? I thought it might be some kind of jar problem, so that's good.
> 
> Cheers,
> Adrian.
> 
> 
> On 23 October 2013 23:32, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
>> Yeah I was looking into this then ran out of time so Anthony took over. What matt said, build order.
>> Cheers
>> S
>> sent from mobile device
>> On 24/10/2013 9:08 AM, "Matthew Jones" <matthew at longsight.com> wrote:
>>> Because it failed to compile, and signup was the tool immediately after it in the pom. This was something Steve appeared to be working on and started so I didn't give it much attention.
>>> 
>>> The email on that list included an Adam which I mistakenly thought was Adrian, and it also didn't include a list. Must have been a bad week.
>>> 
>>> 
>>> On Wed, Oct 23, 2013 at 5:48 PM, Adrian Fish <adrian.r.fish at gmail.com> wrote:
>>>> What off list discussion? How did it stop signup from working?
>>>> 
>>>> Adrian.
>>>> 
>>>> 
>>>> On 23 October 2013 22:24, Matthew Jones <matthew at longsight.com> wrote:
>>>>> Looking through my emails, it looks like there was an off-list discussion where roster2 was removed because it wasn't compatible and it stopped signup from working so we removed it last week. I didn't notice until now that this wasn't on the list. 
>>>>> 
>>>>> But if you've fixed it, go ahead and re-add it, no real discussion needed. Everything that is removed from experimental was just because it waan't updated for the 2.10 pom changes.
>>>>> 
>>>>> 
>>>>> On Wed, Oct 23, 2013 at 4:50 PM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
>>>>>> No objections from me.  In my experience, Roster2 encompasses all of the existing behavior of Roster1 plus adds in easier-to-configure official photo support including photos from LDAP and photos in a directory structure.  
>>>>>> 
>>>>>> --Sam
>>>>>> 
>>>>>> 
>>>>>> On Wed, Oct 23, 2013 at 4:46 PM, Anthony Whyte <arwhyte at umich.edu> wrote:
>>>>>>> There is interest in retiring the roster module in favor of roster2 in the next trunk-based release.  This morning, I tweeked roster2's poms and dropped it's assembly in order to align it with recent trunk changes.[1]  I'd like to add it to the experimental build so that it can be more easily evaluated as a replacement candidate.  This involves 1) uncommenting the roster2 line in .externals, 2) referencing the module in the base pom <modules> experimental build section and 3) adding any additional roster2 specific properties that Steve or Adrian think worth activating to experimental.sakai.properties (assuming of course Nightly2 experimental still reads this file and appends its properties to its local sakai.properties during the build process).
>>>>>>> 
>>>>>>> Does anyone object if I add roster2 to the experimental build?  I plan to make the change on Friday, 23 Oct 2013. 
>>>>>>> 
>>>>>>> Cheers,
>>>>>>> 
>>>>>>> Anthony
>>>>>>> 
>>>>>>> 
>>>>>>> [1] https://jira.sakaiproject.org/browse/RSTR-66
>>>>>>> [2] Properties: https://confluence.sakaiproject.org/display/RSTR/Roster2
>>>>>>> [3] https://source.sakaiproject.org/svn/config/trunk/configuration/bundles/src/bundle/org/sakaiproject/config/bundle/experimental.sakai.properties
>>>>>>> 
>>>>>>> anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu | 517-980-0228
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> cle-release-team mailing list
>>>>>>> cle-release-team at collab.sakaiproject.org
>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> cle-release-team mailing list
>>>>>> cle-release-team at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> cle-release-team mailing list
>>>>> cle-release-team at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>>> 
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131028/526f2eaa/attachment.html 