ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-741) Enhance report task such that dependency graphs can show the original constraint rule on graph edges and resolved specific revision number on graph nodes
Date Tue, 26 Feb 2008 18:26:51 GMT

    [ https://issues.apache.org/jira/browse/IVY-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572591#action_12572591
] 

Xavier Hanin commented on IVY-741:
----------------------------------

OK, so I think this is not an issue, the change in report you want will be a side effect of
the changes in IVY-740. But since we will now have more information in metadata, I suggest
keeping this issue to actually improve the metadata when normal resolve mode is used, to display
the original version contraint as I suggest in my previous comment. 

Does it make sense?

> 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.


Mime
View raw message