Ok so, thanks for explaining it. The other reason I suggested it was because my project is using artifacts from cxf, servicemix and camel. I ended up with a mix of 2.5.5 and 2.5.6, and I end up with method signature clashes :(. I can live with more stringent depenedencies in my poms until everyone harmonises on 2.5.7.
Regards Eamonn > From: [email protected] > To: [email protected] > Subject: Re: move up to springframework 2.5.6? > Date: Wed, 4 Nov 2009 11:04:57 -0500 > CC: [email protected] > > On Wed November 4 2009 10:43:38 am Eamonn Dwyer wrote: > > Hi > > is there a reason we are using version 2.5.5 of spring framework? I think > > servicemix and camel have already moved on up to 2.5.6, so would it be a > > good idea to upgrade to both stay in synch with them and also to avail of > > any bug fixes. > > Spring 2.5.6 has a "bug" in the JMS stuff that is resulting in stack traces > being printed out in several places when running out test suite. We've more > or less stayed on 2.5.5 so that those stack traces aren't confused with real > errors. > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog _________________________________________________________________ New Windows 7: Find the right PC for you. Learn more. http://windows.microsoft.com/shop
