[Building Sakai] [WG: Sakai QA] Upgrade to Spring 2.5.6

David Horwitz david.horwitz at uct.ac.za
Thu Apr 9 09:53:15 PDT 2009


-1 its way to late to get this in and tested properly before the 2.6
release. There are also people relying on the 1.0 kernel for production.
We can't really decide if this is safe for a later 2.6 release until we
have tested more, but my gut feel is a no.

David

Mustansar Mehmood wrote:
> after looking at the patch  by Zach
> Thomas,(http://bugs.sakaiproject.org/jira/browse/SAK-16029) it seems
> changes are limited to pom files. sakai 2.6 could be a candidate for
> this patch. ?
> Noah Botimer wrote:
>> It may be worth pulling commons-codec into shared as part of this.
>> There is part of it included as source in util, then packed as a jar
>> dependency at different versions in other places. It should be
>> straightforward to clear these up.
>>
>> Thanks,
>> -Noah
>>
>> On Apr 9, 2009, at 4:25 AM, David Horwitz wrote:
>>
>>> I was going to send out a mail immediately after 2.6.x was released
>>> to suggest we upgrade a range of libraries then, so we have a long
>>> testing lead before 2.7 my list now includes:
>>>
>>>
>>> 1) Spring
>>> 2) commons-lang
>>> 3) javax.mail/activation
>>>
>>> Any others?
>>>
>>> David
>>>
>>> Mustansar Mehmood wrote:
>>>> +1
>>>> I think it is always a good idea to move to new libraries for sake of
>>>> getting rid of bugs
>>>> introducing new technologies which will invite wider community
>>>> development enthusiasts to join sakai development/integration
>>>> community
>>>> --mustansar
>>>> Zach A. Thomas wrote:
>>>>  
>>>>> Hi everyone. I have submitted two patches (one for kernel trunk,
>>>>> one  for sakai trunk) to upgrade this ball of wax to Spring 2.5.6.
>>>>>
>>>>> Aaron Zeckoski very helpfully provided me with an update of
>>>>> generic- dao which was necessary to make this work.
>>>>>
>>>>> Any comments are welcome. My motivation for doing this is that it
>>>>> is a  pre-requisite for what I _really_ want to do, which is
>>>>> provide full  support for Grails as a tool-development stack for
>>>>> Sakai.
>>>>>
>>>>> Here's a summary of changes in 2.5.0, and of course there have
>>>>> been  plenty of fixes since then:
>>>>> http://www.springsource.org/node/561
>>>>>
>>>>> If these patches are deemed worthy, they must both be applied at
>>>>> the  same time for trunk to remain alive and kicking:
>>>>> http://bugs.sakaiproject.org/jira/browse/KNL-150
>>>>> http://bugs.sakaiproject.org/jira/browse/SAK-16029
>>>>>
>>>>> cheers,
>>>>> Zach Thomas
>>>>> Owner, Aeroplane Software LLC
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>
>>>>> TO UNSUBSCRIBE: send email to
>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>>> "unsubscribe"
>>>>>
>>>>>       
>>>>   
>>> _______________________________________________
>>> sakai-qa mailing list
>>> sakai-qa at collab.sakaiproject.org
>>> <mailto:sakai-qa at collab.sakaiproject.org>
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-qa-unsubscribe at collab.sakaiproject.org
>>> <mailto:sakai-qa-unsubscribe at collab.sakaiproject.org> with a subject
>>> of "unsubscribe"
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>
>


More information about the sakai-dev mailing list