Primarily, <dependencyManagement> does not actually attach an artifact dependency to a given project, while declaring a <dependency> does exactly that.
So you could have a project with 10 items in depMgmt and no deps which tells users (and Maven) that it can be built all on its own. Wayne 2008/10/8 陈思淼 <[EMAIL PROTECTED]>: > <dependencyManagement> > <dependencies> > <dependency> > <groupId>test</groupId> > <artifactId>d</artifactId> > <version>1.0</version> > </dependency> > </dependencies> > </dependencyManagement> > > > <dependencies> > <dependency> > <groupId>maven-test</groupId> > <artifactId>a</artifactId> > <version>1.0</version> > <scope>runtime</scope> > </dependency> > <dependency> > <groupId>maven-test</groupId> > <artifactId>c</artifactId> > <scope>runtime</scope> > </dependency> > </dependencies> >
