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

[Matthew Jones]

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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131023/7a992d91/attachment.html