Updating classpath container

In other words, when workspace resolution is enabled, project's don't have to be installed in the local repository to relate to one another. This has the effect of telling m2eclipse to stop trying to manage your project's classpath, and it will remove the Maven Dependencies classpath container from your project.

If you do this, you are essentially on your own when it comes to managing your project's classpath.

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.

Figure 7.1, “Manually Adding a Dependency to the Project's POM” shows how I added a dependency for into the query field, m2eclipse queries the repository indexes and even shows a version of the artifact that is currently in my local Maven repository.

I have successfully installed Maven plugin for my eclipse 3.4.0 ganymede and imported my parent project, su project and sa project. Take a look at the Problems tab in Eclipse and see if there's any more detail to the error. Bruce -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E G-NAn unsatisfied dependency is a prerequisite for installing m2eclipse.0 Requirement is that it was created with the similar wtp settings as the reactor projects, but the project name template my differ.Create an ANT_HOME environment variable to point the directory ${ant. 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.