Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354247 - Cannot downgrade to Spring 2.5.6 following Virgo FAQ
Summary: Cannot downgrade to Spring 2.5.6 following Virgo FAQ
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: documentation (show other bugs)
Version: 3.0.0.RC1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Chris Frost CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-09 09:23 EDT by Hristo Iliev CLA
Modified: 2011-09-28 06:59 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hristo Iliev CLA 2011-08-09 09:23:50 EDT 
Downgrade to Spring 2.5.6 is not possible (following Virgo FAQ) due to the dependency range "[2.1.0, 3.0.0)" in Spring Framework.

Since Tomcat is already at version 7.0 we have javax.servlet* packages at 3.0 which is outside the Spring Framework required range.
Comment 1 Hristo Iliev CLA 2011-09-01 11:17:55 EDT 
Virgo FAQ is updated with instructions to use Virgo Jetty Server or Virgo 2.1.x
Comment 2 Hristo Iliev CLA 2011-09-26 07:36:25 EDT 
I think we can close this one since the rest of the work is detailed by bug 357273 - shift the ranged supported by Virgo
Comment 3 Chris Frost CLA 2011-09-28 06:59:33 EDT 
I have shifted the version ranges, closing as done.