Eclipse updating maven dependencies hangs
You can configure a project to resolve dependencies from a workspace.
This has the effect of altering the way that Maven locates dependency artifacts.
If workspace resolution is disabled, the m2eclipse Maven build for 's artifact is present in the local repository.
(Please note that the functionality for adding a dependency or a plugin is exactly the same so we’ll demonstrate it by adding a dependency.) m2eclipse offers two options for adding dependencies to a project.
The first option is by manually editing the file to add a dependency is that you must already know the information about the artifact, or use the features discussed in the next section to manually locate the artifact information in the repository indexes.
The upside is that after manually adding the dependency and saving the , the project’s Maven Dependencies container will be automatically updated to include the new dependency.
This option is preferred because it is such a tremendous time saver.With m2eclipse, you no longer need to hunt through the central Maven repository for an artifact version.Select this option, and m2eclipse will attempt to download the source artifact from the Maven repository.If it is unable to retrieve this source artifact, you should ask the maintainers of the project in question to upload the appropriate Maven source bundle to the central Maven repository.If a project is configured to resolve dependencies from the workspace, these artifacts do not need to be present in your local repository.
Assume that project-a and project-b are both in the same Eclipse workspace, and that project-a depends on project-b.