I have a java application that requires the latest commons-dbcp version (1.3) and it's db connection pool is configured by Spring. This application is but one of a list of applications in the same tomcat (a suite if you like) and many of them use an older version of commons-dbcp (1.2.1), all configured by Spring.

So, while I can compile (with Maven) my application with DBCP 1.3, I can't run it because Spring is trying to configure my db connection pool with the old version, which is in /shared/lib in Tomcat.

The problem I have is that I do not have time, nor the approval, to upgrade everything to 1.3, just the one application I'm fixing. Is it possible to force Spring, in the components.xml file of my application (or by some other means) to the new DBCP version so that only it will run the new version and not affect any other application?