Eclipse updating maven dependencies disable
Once you have added a project repository and clicked on the refresh icon in the Maven Respositories view, you will be able to view the project-specific repository and manipulate the repository index for this project-specific repository.
The Maven Repostitories view allows you to browse and manipulate your local Maven repository index.
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 m2eclipse is using a remote repository, it will download a Nexus index from the remote repository.
If m2eclipse is managing a local repository (local or workspace) it will use the open source Nexus indexer to create and maintain a local index.
To demonstrate this feature, add a repository element to a pom.xml, by loading the Form-based POM Editor and clicking on the Repositories tab.
Click on the "Create..." button and add a new repository with the following values as shown in Figure 6.11, “Adding a Repository to a Project's POM”.
If your organization maintains a number of specialized, segregated repositories that hold snapshots, you may not want to include these artifacts in simple searches for artifacts that contain a particular identifier or class.
If the central Maven repository contains a source artifact for a particular project, you can download the source from the repository and expose it to the Eclipse environment.
When you are trying to debug a complex issue in Eclipse, nothing can be easier than being able to right click on a third-party dependency and drill into the code in the Eclipse debugger.
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.
m2eclipse maintains an index of artifacts generated by your Eclipse workspace.