Import local Maven projects
Local Maven project can be imported using Elipse import wizard. Select "File / Import..." and then choose "Maven Projects" from the list.
Then on the next wizard page specify root folder to scan for projects, then hit "Refresh" button. Then you can check projects for importing into the Eclipse workspace. Note that project modules are shown as nested elements.
By default modules will be imported as separate projects and workspace artifact resolution will be enabled, but you can adjust these options from the Advanced section.
- The major advantage of single project is that it less verbose and it may work little better with some Team VSC plugins. For example, Sublipse is little shaky when working with overlapping nested projects.
- From the dependency resolution point of view, multi-project setup allow to be much closer to the Maven dependency resolution and provides more accurate dependencies for each module.
Checkout Maven projects from SCM
Maven projects can be checked out from Source Control Management system (SCM) using Eclipse import wizard from "File / Import... / Other / Checkout Maven projects from SCM...". Then you can select SCM type from the list of supported SCMs, specify URL, required revision or tag and select location where code should be checked out.
 | You can paste a Maven SCM URL like "scm:git:http://repo.or.cz/r/egit.git" directly into the "SCM URL" field |
Materialize Maven projects
Full projects for Maven artifacts that have correct SCM information specified in their POM can be checkout into Eclipse Workspace using import wizard from "File / Import... / Other / Materialize Maven Projects...". Then you can use "Add..." button and use Quick Search to add Maven artifacts for import. Then if selected artifacts have correct SCM info specified they will be imported in Eclipse workspace.
| The same import wizard can be also invoked from the Maven Indexes view and also from "Maven / Import Project" popup menu on any jars in Eclipse Workspace. If selected jars are not in "Maven Dependencies" classpath container, then plugin will try to identify Maven artifacts using SHA1 of selected jars. |
