[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-27: ------------------------------------------ That's an interesting interpretation as well. So far I've stubbed out an API for this in my tree: {code}public void dependencyInfo() { final ArtifactInfo longhand = DependencyResolvers.use(MavenResolverSystem.class).resolve("G:A:V") .withoutTransitivity().asSingle(ArtifactInfo.class); final ArtifactInfo shortcut = Maven.RESOLVER.resolve("G:A:V").withoutTransitivity() .asSingle(ArtifactInfo.class); final MavenCoordinate coordinate = shortcut.getCoordinate(); final String groupId = coordinate.getGroupId(); final String artifactId = coordinate.getArtifactId(); final String version = coordinate.getVersion(); final String resolvedVersion = shortcut.getResolvedVersion(); final String type = shortcut.getType(); final boolean isSnapshot = shortcut.isSnapshotVersion(); final String classifier = shortcut.getClassifier(); final File file = shortcut.getArtifact(FileFormatProcessor.INSTANCE); final File file2 = shortcut.getArtifact(File.class); final InputStream in = shortcut.getArtifact(InputStreamFormatProcessor.INSTANCE); final InputStream in2 = shortcut.getArtifact(InputStream.class); final JavaArchive archive = shortcut.getArtifact(new ArchiveFormatProcessor<JavaArchive>(JavaArchive.class)); }{code} I think both are valid use cases. So I'll make another issue for the case that Karel notes above, and modify this issue to more clearly reflect the case I'd posted here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira