pi song wrote:
I just had a look at Mercury artifact resolver. It currently returns a list
of artifacts.
Mercury has the following resolution APIs - see DependencyBuilder interface:
- buildTree - creates a full metadata tree
- resolveConflicts has two flavors
-- List<ArtifactMetadata> resolveConflicts( MetadataTreeNode root ) to
create the classpath set
-- MetadataTreeNode resolveConflictsAsTree( MetadataTreeNode root )
for tool integration, reduces the full tree into resolved tree
At this stage APIs are experimental (it's still alpha product) and are
subjected to change as we go on with Maven integration.
Please feel free to register any suggestions/requirements in Mercury jira:
http://jira.codehaus.org/browse/MERCURY
Thanks,
Oleg
I think you will need a middle man to help expose that list as simplified
tree anyway (for plug-in developers).
Am I right? Just want to understand a bit more.
Pi Song
On Tue, Feb 17, 2009 at 8:05 PM, Mark Hobson <markhob...@gmail.com> wrote:
2009/2/16 pi song <pi.so...@gmail.com>:
I have just noticed that Maven3 is on the way. The new dependency
resolver
really looks very interesting. Just curious how would that affect
maven-shared/maven-dependency-tree. Will this API stay the same or be
replaced?
I'd personally be in favour of mercury superseding
maven-dependency-tree. It only existed to provide a tree API around
the pre-existing event API, and since mercury is tree-based it should
hopefully now be rather redundant.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
