Updating the springframework to version 3.11 RELEASE inside VTShttps://www.eclipse.org/forums/index.php/mv/msg/361599/885555/#msg_885555
I have been learning how to use VTS these weeks and i am kind of stuck when i try to update the version of springframework inside VTS.

I found that simply droping the libd files into the /virgo-tomcat-server-3.0.3.RELEASE/repository/usr directory will cause a conflict on startup,something like this :

package 'org.springframework.core.io_3.0.5.RELEASE' in bundle 'org.springframework.core_3.0.5.RELEASE[25]' used by 'org.springframework.osgi.context_1.2.1' in bundle 'org.springframework.osgi.core_1.2.1[29]'
conflicts with 'org.springframework.core.io_3.0.5.RELEASE' in bundle 'org.springframework.core_3.0.5.RELEASE[1339576458771]' used by 'org.springframework.context_3.0.5.RELEASE' in bundle 'org.springframework.context_3.0.5.RELEASE[1339576458762]'
-----------------------------------------------------------------------------

It seems that the version used inside VTS will conflict with the latest version of libd files i drop in the repository,but i don't know why?

And if i want to use version 3.1.1 RELEASE in my applications,how can i configure VTS to avoid the conflict of packages?

It will be really nice if your guys can help me.]]>lee lee2012-06-13T08:41:34-00:00Re: Updating the springframework to version 3.11 RELEASE inside VTShttps://www.eclipse.org/forums/index.php/mv/msg/361599/885566/#msg_885566
bug 378470 . This bug will not be implemented in Virgo 3.5.0, but we are looking to implement it in a later release. Meanwhile, I'm afraid you'll need to stick with Spring 3.0.x. (The only alternative before then would be to start with Virgo nano, which does not include Spring framework, and add Gemini Blueprint 1.0.1.M01 and Spring 3.1.x, but this is quite a different solution to VTS.)]]>Glyn Normington2012-06-13T08:56:50-00:00