i'm new to maven, but have decades of experience with builds and java. after a basic survey of maven, one of the first things i asked my self is how i could force a version of a dependency at the parent pom.
the general use case is that you are working with a series of third-party dependencies (and their respective poms) that specify conflicting versions of a particular library commons-logging for example, and you want to force a specific version that you know you will be running with. let's say you want to verify behavior of those third party dependencies with this specific version using the test goal. i did some research and found some mailing list archives which basically said this wasn't supported and that the technique to address this would involved the use of exclusions, but you may end up having to exclude the same transitive dependency across multiple direct dependencies. this seems to violate the "don't repeat yourself" (DRY) principle, and i was wondering why there wasn't some thing like an "override" flag for dependencies in the "dependencyManagement" section to provide the option to ratchet down the version of a potentially repetitively occurring transitive dependency in one fell swoop. i came up with a round about way of accomplishing that by declaring a pom-type dependency, and specifying the exclusion there, but it seems on the awkward side. so basically, i just wanted to verify this behavior and ask if anyone was aware of any outstanding jira entries requesting this type of feature, or if this is an old topic that has been dismissed as a improper or something. thanks,tony. -- View this message in context: http://www.nabble.com/dependency-version-at-pom-level-tp24046046p24046046.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
