Borked dependency graph?

[Kevin Menard]

I'm working on some Cayenne plugins for maven that should hopefully make 
working with the two much nicer.  I'm been having a hell of a time with 
classpath-related issues.  I just cracked open the parent POM and see 
some dependencies are listed as being provided that we directly rely 
on.  Could someone please cast some light on this issue?  My guess is 
that they're listed as provided because some other dependency has a 
transitive dependency on the same libs.  If this is the case, I propose 
we change this so that the dependency graph reflects what Cayenne 
actually depends on.  The maven book describes ways for handling this.  
Incidentally, changing those libs from "provided" to "compile" (default) 
fixes my classpath woes.  So, there may be a maven-related bug here, 
too, since transitive dependencies are supposed to be followed.

Any insight would be appreciated, since I missed most of the maven 
migration.

Thanks,
Kevin