Virgo is more conservative than Spring DM. We assume that backward incompatibilities may be introduced by Spring 3.1 whereas Spring DM assumes sufficient backward compatibility right up until Spring 4!
Your point about the version of Spring being unchecked is interesting. Of course there will be some resolution failures which will give a pretty strong hint, but there is no simple event log messages which says "Your version of Spring is too high". I suppose a check could be added during user region initialisation. Please file a bug if you would like to see that.
At some stage, we are going to be looking for people to fix some of these bugs. ;)
Dmitry Sklyut Messages: 252 Registered: January 2010
Senior Member
Bugzilla: 311900
I think in short term a version matrix should be enough.
But the burden is on you to commit the code so we can start looking at it :) . With change in packaging it would be much harder to try to address it in both places (dm-server and virgo code base)