THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Where Queries is nothing else but the <dependencies> element contents from Arifact's POM. Each dependency i.e. query is then expanded into children list via calling PomDependencyDataSource MetadataSource. Various implementations of the latter are supposed to return back all available artifacts, matching the query criteria.
...
- *ArtifactFilter*s - the ones that are called during tree building. They will be able to veto any artifacts from being added to the tree
- *ArtifactSorter*s - contributors, that define preferences during conflict resolution. They just favor this or that artifact, but cannot completely ban it. So if no better solution exists - the bad one will be selected.
The process s also enhanced by the ability to chain MetadataSource implementations, so when m2eclipse needs to make our new resolver aware of the workspace projects - it simply inserts the specific MetadataSource at the head of the chain
| Anchor | ||||
|---|---|---|---|---|
|
OSGi Resolution
...