m2eclipse uses the downloaded index for all types of searches. The index is downloaded from the remote repo(s). As you've installed the artifact in your local repo, it doesn't exist in the index. To fix this, get yourself a repo manager (like Nexus) and deploy the artifacts there. Then configure it to produce a downloadable index.
/Anders On Tue, Sep 6, 2011 at 19:18, KARR, DAVID <[email protected]> wrote: > I had to install the Oracle JDBC driver (ojdbc6) in my local repo for my > integration tests. I ran "install:install-file" from the command line to > install it, and then I inspected the hierarchy that created. It looks > correct to me. > > I then went back into Eclipse and tried to add a new dependency. When I > entered "ojdbc" in the filter, it didn't show the new artifact that I > installed. I tried clicking the "Refresh" icon in the graphical view of the > POM. I also tried selecting "Update Dependencies" from the Maven context > menu on the project. Neither of these made any difference. > > I then manually installed the dependency reference in my POM and ran my test. > It worked fine. > > Is there anything else I should have done to refresh what plugins are > available to populate in that list? > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
