Hi, I'm using version 0.0.10 of the plugin on eclipse 3.2.2.
I have a number of projects that share a common parent pom, with the various shared configuration settings. I've just changed the parent pom to include the dependencyManagement section and my child poms to not include specific versions in their dependencies unless they have to override the global default from the parent. This works fine when running mvn from the command line. However, there's a problem with the jars included via the Build Path -> Maven2 Dependencies route. Basically, it always uses the version of an artifact specified in the parent pom even when the version is overridden by the child dependency. Is this a known problem? Are there some configuration options or steps I'm missing? Thanks Jonny -- View this message in context: http://www.nabble.com/dependencyManagement-problem-tf3435153.html#a9577250 Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
