[Building Sakai] Alert: Moving spring-webmvc out of shared

[David Horwitz]

I did some testing and fixing of the trunk checkout (see 
https://jira.sakaiproject.org/browse/SAK-20781) So that all tools that 
require spring-webmvc in core correctly declare so in their tool poms. I 
further tested a number of the RSF tools that needed updating and all 
seemed to work fine ...

D

On 06/29/2011 01:45 PM, Steve Swinsburg wrote:
> +1. In addition, developers of contrib or local tools should perform their own checks to ensure that they are not depending on spring-webmvc being provided.
>
> cheers,
> Steve
>
> On 29/06/2011, at 7:54 PM, David Horwitz wrote:
>
>> Hi All,
>>
>> Please see https://jira.sakaiproject.org/browse/KNL-757
>>
>> This concerns moving spring-webmvc out of shared and allowing webapps to
>> package their own  versions and thereby allow more flexibility in UI
>> work. Testing indicates that the change will is fairly trouble free with
>> one caveat. That is that a small number of tools may have an undeclared
>> runtime requirement for spring-webmvc, these webapps will fail on start
>> up with a Classnotfound error relating to a spring class. Adding
>> spring-webmvc to the tools pom so its packaged in the webapp fixes this.
>>
>> Unless I hear otherwise from the list I will commit this on Saturday
>> morning GMT+2
>>
>> David
>> _______________________________________________
>> 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"