Thanks Martin, I like the exclusion option. Giving that a try now. Sure I will
go with one or the other.Best regards Ken in nashua
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: T-4.1.6-SNAPSHOT broken?
commons-poolDate: Wed, 10 Sep 2008 13:53:35 -0400
Well Still no solution except for
Well Still no solution except for brute force specifying commons-pool-1.4 in my
webapp pom.
commons-dbcp-1.2.2 has nothing to do with it but shows up as a parent in the
tree for it.
Still do not know whats pulling commons-pool-1.3 in.
Here is the tree...
I'm not sure why Maven would favor 1.3 over 1.4... You could either
explicitly add commons-pool 1.4 to your pom, or exclude 1.3 from your
commons-dbcp dependency so that it will be ignored. Off the top of my
head, something like this:
dependency
...
artifactIdcommons-dbcp/artifactId
Perhaps it's not much help, but you can see where commons-pool comes from
if you run:
mvn dependency:tree
Martin
On Tue, 09 Sep 2008 19:56:31 +0200, Ken in nashua
[EMAIL PROTECTED] wrote:
Well no where in my project is commons-pool specified anywhere. It is
implicitly being drawn
please make sure that there's exactly one version of commons-pool on your
classpath (1.4). --Marcus
