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>
   ...
   <artifactId>commons-dbcp</artifactId>
   ...
   ...
   <exclusions>
      <exclusion>
         <groupId>commons-pool</groupId>
         <artifactId>commons-pool</artifactId>
      </exclusion>
   </exclusions>
</dependency>


Martin


On Wed, 10 Sep 2008 19:45:29 +0200, Ken in nashua <[EMAIL PROTECTED]> wrote:


Thanks alot martin... that helped alot.
The tree showed me that T-4.1.6 was pulling in commons-pool-1.4
AND
[INFO] | +- commons-dbcp:commons-dbcp:jar:1.2.2:compile[INFO] | | \- commons-pool:commons-pool:jar:1.3:compile
commons-dbcp was pulling in commons-pool-1.3
commons-1.3 is being war'd up into my webapp ... not commons-1.4
Thats whats causing havoc.
I did confirm if I include commons-1.4 in my dependencies for my webapp it ends up in my war file and all is well.
So maybe I need to upgrade commons-dbcp ?
- cheers
Best regards Ken in nashua



From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: T-4.1.6-SNAPSHOT broken? commons-poolDate: Tue, 9 Sep 2008 13:56:31 -0400


Well no where in my project is commons-pool specified anywhere. It is implicitly being drawn into the project somehow and war'd up within web-inf/lib I had to explicitly specify commons-pool-1.4 explicitly as a dependency in the pom. And after running jetty;run with --debug I noticed a log text [DEBUG] commons-pool:commons-pool:jar:1.3:compile (removed - nearer found: 1.4) as well as similar log messages for other commons libraries. Specifying the canonical revision that tapestry uses solved the issue but it would be nice to know what mechanism is drawiing in commons-pool-1.3 when it is never specified within the pom. This all seems unnecessary. Any comments would helpBest regards Ken in nashua

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to