"ALRubinger" wrote : From the Maven Release Notes: | | "http://maven.apache.org/release-notes.html" wrote : MNG-3220 - There is now a new scope for importing managed dependencies. See here{1} and here{2} for details. Please note that the use of this scope will break backwards compatibility with older Maven versions. If you use this, you should use the maven-enforcer-plugin to require a minimum maven version of 2.0.9 | | Still interpreting what this means. | | S, | ALR | | References: | | {1} - http://docs.codehaus.org/display/MAVEN/Importing+Managed+Dependencies | {2} - http://maven.apache.org/guides/introduction/introduction-to-dependency-me... | As far as I understand it, the import scope imports just dependencyManagement information (versions, excludes, etc) from another project, and not the dependencies themselves. Are you using the import scope in ejb3? I'm not sure how maven 2.0.8 would handle import scope, either an error or unpredictable behaviour I would guess. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154275#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...