Hi, dependencyManagement is inherited by children POMs. It is useful to define a dependency within dependencyManagement tag expliciting the version there. Then in the children POMs you can just declare your dependecy without having the version tag
have a look here: http://maven.apache.org/pom.html#Dependency%20Management bye, Federico Gregory Kick-2 wrote: > > I have a question about the behavior of the <dependencyManagement> > portion of a POM as it relates to plugin dependencies. > > Say I have: > ... > <dependencyManagement> > <dependencies> > <dependency> > <groupId>GROUP</groupId> > <artifactId>ARTIFACT</artifactId> > </dependency> > </dependencies> > </dependencyManagement> > ... > > And in some project that inherits from this pom, > <plugin> > ... > <dependencies> > <dependency> > <groupId>GROUP</groupId> > <artifactId>ARTIFACT</artifactId> > </dependency> > <delendencies> > ... > </plugin> > will fail with a missing version. > > Is this the expected behavior or is this a bug? > > > -- > Gregory Kick > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/dependency-management-within-plugin-dependencies-tf2772190s177.html#a7735149 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
