[MNG-7993] New or existing service improvement: "resolve in the context of project"

**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MNG-7993](https://issues.apache.org/jira/browse/MNG-7993?redirect=false)** and commented

See for example MCOMPILER-391.
Today all the burden is on plugin to reimplement all the logic whether to apply or not the depMgt. Instead, there should be a service that does "resolve in the context of project" (obeying all the depMgt), so a plugin that has GAV artifact dependency can just pass it to API and API resolves with while obeying existing depMgt entries present in project.

---
No further details from [MNG-7993](https://issues.apache.org/jira/browse/MNG-7993?redirect=false)

Start by reading the MCOMPILER-391 example and the linked MNG-7993 discussion. Identify the existing dependency-resolution API and how project dependency-management entries are applied. Done means a service exists that accepts a GAV artifact dependency and resolves it in the project context while obeying those entries.

Written by the indexing model from the issue text.