[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-27) Allow for full dependency info from MavenDependencyResolver::resolve
Michal Matloka (JIRA)
jira-events at lists.jboss.org
Fri Nov 2 11:39:18 EDT 2012
[ https://issues.jboss.org/browse/SHRINKRES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731174#comment-12731174 ]
Michal Matloka edited comment on SHRINKRES-27 at 11/2/12 11:39 AM:
-------------------------------------------------------------------
Assuming that we're resolving the following structure of dependencies
* some pom
** parentA
*** childAA
*** childAB
** parentB
Currently executing as File/InputStream/ResolvedArtifactInfo results in list { parentA, childAA, childAB, parentB }.
Aether allows to read this not in form of such list but in form of graph (which may contain .pom's in its structure). So this complicates a little, becasue as(ResolvedArtifactInfo.class) can result in one element (pom) (one element list?) with getDependencies(); ({ parentA, parentB } and both them having their dependencies) instead of { parentA, childAA, childAB, parentB } (still used for File and InputStream) ?
Then inside our implementation we have to keep both types of representations (list and graph) and pass them to FORMATSTAGETYPE (instead of current Collection<Artifact> ).
was (Author: mmatloka):
Assuming that we're resolving the following structure of dependencies
* parentA
** childAA
** childAB
* parentB
Currently executing as File/InputStream/ResolvedArtifactInfo results in list { parentA, childAA, childAB, parentB }.
Aether allows to read this not in form of such list but in form of graph. So I assume as(ResolvedArtifactInfo.class) should result in list of { parentA, parentB } with getDependencies(); instead of { parentA, childAA, childAB, parentB } (still used for File and InputStream) ?
Then inside our implementation we have to keep both types of representations (list and graph) and pass them to FORMATSTAGETYPE (instead of current Collection<Artifact> ).
> Allow for full dependency info from MavenDependencyResolver::resolve
> --------------------------------------------------------------------
>
> Key: SHRINKRES-27
> URL: https://issues.jboss.org/browse/SHRINKRES-27
> Project: ShrinkWrap Resolvers
> Issue Type: Feature Request
> Components: api-maven, impl-maven
> Affects Versions: 2.0.0-alpha-2
> Reporter: Ales Justin
> Assignee: Michal Matloka
>
> It would be useful to be able to grab full dependency info, not just files.
> e.g. name, version, import type, etc
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the shrinkwrap-issues
mailing list