Never saw that. Workspace projects won't be resolved either if you have workspace resolution disabled or if dependency versions won't match projects in workspace. Also note that dependent projects should have Maven support enabled.
Anyway, it is better to ask questions specific to m2eclipse in m2eclipse users mailing list. See http://m2eclipse.codehaus.org/mail-lists.html regards, Eugene jwcarman wrote: > > We've got a multi-module maven-based project and we're trying to import it > using m2eclipse. Everything seems to be working fine, but it's not > setting > up the classpath correctly for projects that depend on other projects, it > seems. Is this a known issue? > -- View this message in context: http://www.nabble.com/m2eclipse-and-inter-module-dependencies...-tp19577444p19577759.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
