The Sonatype blog republished a tip from October 2009 in their best of series (see http://www.sonatype.com/people/2009/10/maven-tips-and-tricks-grouping-dependencies/) that didn't use scope import for specifying a POM dependency. I tried this with 3.0 and it works and avoids the warning (see below).
The confusing thing is that the Maven documentation indicates that scope=import should be used for POM dependencies (see http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope). Is this a case of using POM dependencies in dependencyManagement vs build? gabe97330 wrote: > > I'm using maven 3.0-alpha-3 and getting a warning on use of dependencies > of > scope import in sub-modules although everything works as it did in 2.x. > there a way to address this warning either through correcting my usage > (assuming it is a valid warning) or some sort of pragma to turn off the > warning? > > Thanks, > > Gabe > > > ----- > > Blog: Gabe's Groove > Twitter: Gabe97330 > ----- Blog: http://gabe97330.begeddov.com Gabe's Groove Twitter: http://twitter.com/gabe97330 Gabe97330 -- View this message in context: http://old.nabble.com/maven-3-warning-on-dependency-scope-import--tp26385938p27308001.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
