This may be possible, but I don't believe anyone has tested this. The next FUSE release is currently targeting the 2.5.6.SEC01 Spring version.
A constraint violation in this context usually means that there is a Require-Bundle or an Import-Package that fails, either due to the requirement not being present in the OSGi container at all, or being present but outside the required version range.
In either case, you will need to drill into it a bit to find out what constraint is actually failing, and start looking at updating/adding bundles to resolve it. Check logs and all that, and look at the MANIFEST.MF in the Spring bundle where the constraint is failed...
Is there progress on this issue? Is the Progress team planning on upgrading to Spring 3 (potentially Spring DM 2) any time soon? I verified that having both spring 2.5.6.SEC01, 3.0.0.RELEASE together on FUSE 4.2.0 causes problems.
Bump for this thread.
Is there any plan for Spring 3 support? We're considering a move to FUSE and need to unwind our use of Spring 3 annotations if Spring 3 is not supported.