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 Sat, 23 Feb 2008 10:11:19 GMT

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

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

I don't think we can simply drop the revision constraint actually used in favor of the original
version constraint, unless when you'd use the resolve mode introduced by IVY-740. Indeed it
would be difficult to understand why Ivy picked version 1.3 of a component where the version
constraint says latest.integration, and when you know there is a version 1.4.

So what could be done is improve the xml report to store both the original and delivered version
constraint. Then in the graph we could indicate both using a text convention. For instance
it could be {{1.3 (latest.integration)}}.

What do you think?

> 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