[
https://issues.apache.org/jira/browse/IVY-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572585#action_12572585
]
Shawn Castrianni commented on IVY-741:
--------------------------------------
Well, the report task is a post resolve task and it is the resolve that will
have this new mode. Therefore, I would expect that if the resolve mode is set
to normal (current behavior), then the report and graph would generate normally
(current behavior) where the 1.3 revision is BOTH on the edge down to a
transitive dependency AND inside the node of the transitive dependency. This
is because in the normal mode, the transitive dependency was resolved by a
specific revision contraint.
However, if the resolve mode is set to original (new mode introduced by
IVY-740), then the report and graph would generate such that the edge of
transitive dependencies would only show the original constraint
(latest.integration, for example) because that is the constraint used to
resolve the transitive dependency AND revision 1.4 would show up inside the
node of the transitive dependency because that is the revision found using
latest.integration.
> Enhance report task such that dependency graphs can show the original
> constraint rule on graph edges and resolved specific revision number on graph
> nodes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IVY-741
> URL: https://issues.apache.org/jira/browse/IVY-741
> Project: Ivy
> Issue Type: New Feature
> Reporter: Shawn Castrianni
>
> After IVY-739 is resolved, ivy will have new metadata that keeps the
> "original constraint rule" metadata in published/delivered ivy files. This
> can be used to enhance the report task. Right now, if you run the report,
> you can see the dependency constraint rules for the direct dependencies of
> the module you are reporting on, but all of the indirect (transitive)
> dependencies are hardcoded to their specific resolved revision numbers.
> Having this extra metadata could allow the report task to put the original
> dependency constraint rules on all the edges in the graph and the resolved
> specific revision numbers inside all of the nodes like it has now. In my
> opinion, that is a better report of the dependencies of a module. It shows
> the constraint rule used and the actual revision found for all nodes in the
> graph.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
