embedded scope is too simplistic #27
Description
We're using embedded scope (a cartographer/atlas invention) to stand for artifacts that are part of the build but which are added via plugin configuration or similar...not the typical provided scope use cases.
However, the single scope does not capture the ways these artifacts are actually used...is the dependency plugin downloading those artifacts to setup a test environment? Or, are they bundled into the shipped artifact?
Having a "shadow" set of scopes that separate these backdoor dependency declarations from regular ones AND tries to figure out how they're used in the build brings up another issue: the complexity of figuring out how they're used. We might be able to infer this from the phase in which the plugin execution runs, but this is inexact at best.