Well I don't agree that dependencyManagement should override what's specified as a hard dependency in the child POM, applying to transitive dependencies is certainly a valid use case: http://jira.codehaus.org/browse/MNG-1577
- Stephen On 7/17/06, David Smiley <[EMAIL PROTECTED]> wrote:
Is there a reason why versions specified in dependencyManagement only apply to dependencies which don't have a version specified? In other words... why not have it specify the dependency regardless of whatever is specified in some child pom? The use case here is for 3rd party pom's transitively brought in like cglib for example. Hibernate depends on cglib... and so does SpringFramework's AOP stuff. I'd like to specify at the top level of my project which version I want chosen without having to introduce a hard dependency via <dependencies> directly since my project does not directly use cglib. -- View this message in context: http://www.nabble.com/-m2--dependencyManagement-question---tf864496.html#a5363288 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
