[ 
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-275:
-------------------------------------------

    Description: 
Spring 3.2.0 has been out for a while now; this new release introduces some 
non-trivial changes to Spring MVC's content negotiation [1].

However, since 3.2.1 (see [2] fore more details), the upgrading issue from 3.1 
is fixed.

[1] 
http://static.springsource.org/spring-framework/docs/3.2.0.RELEASE/spring-framework-reference/html/new-in-3.2.html
[2] https://jira.springsource.org/browse/SPR-10119

  was:
Spring 3.2.0 has been out for a while now; this new release introduces some 
non-trivial changes to Spring MVC's content negotiation [1].

SYNCOPE-286 will remove Spring MVC (but will keep the rest of Spring 
dependencies) so Spring upgrade should be smooth.

[1] 
http://static.springsource.org/spring-framework/docs/3.2.0.RELEASE/spring-framework-reference/html/new-in-3.2.html

        Summary: Upgrade Spring to 3.2.1  (was: Upgrade Spring to 3.2)
    
> Upgrade Spring to 3.2.1
> -----------------------
>
>                 Key: SYNCOPE-275
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-275
>             Project: Syncope
>          Issue Type: Sub-task
>    Affects Versions: 1.0.4, 1.1.0
>            Reporter: Francesco Chicchiriccò
>             Fix For: 1.1.0
>
>
> Spring 3.2.0 has been out for a while now; this new release introduces some 
> non-trivial changes to Spring MVC's content negotiation [1].
> However, since 3.2.1 (see [2] fore more details), the upgrading issue from 
> 3.1 is fixed.
> [1] 
> http://static.springsource.org/spring-framework/docs/3.2.0.RELEASE/spring-framework-reference/html/new-in-3.2.html
> [2] https://jira.springsource.org/browse/SPR-10119

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to