> Ask someone why you have to invoke eclipse:eclipse on toplevel everytime. > If the dependency of some-module has changed, you can NOT invoke > eclipse:eclipse > just on some-module since the plugin then wants to resolve the dependencies > from the repository and adds JAR-Dependencies to the IDE project.
Off topic. Actually I believe this isn't true anymore. See http://jira.codehaus.org/browse/MECLIPSE-344 "all dependent artefacts that are available in your eclipse-workspace will be attached as project references even if they are not in the reactor." It was fixed in 2.5 Can you try it on your project structure and confirm? I know it works for me. I have this structure common projects - module cA ... - module cZ My project - module pA ... - module pZ (where some of these projects depend upon projects from commons) mvn eclipse:eclipse will make sure my module pA references the eclipse project for module cA (and not the jar of cA in the repo) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
