You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "jaikiran pai (JIRA)" <ji...@apache.org> on 2016/12/08 05:25:59 UTC

[jira] [Commented] (IVY-1429) ivy report should contain "branch" info

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

jaikiran pai commented on IVY-1429:
-----------------------------------

Try creating a pull request against the {{master}} branch of this github repository https://github.com/apache/ant-ivy/tree/master and then send a note to the dev list https://ant.apache.org/ivy/mailing-lists.html asking someone to review it.


> ivy report should contain "branch" info
> ---------------------------------------
>
>                 Key: IVY-1429
>                 URL: https://issues.apache.org/jira/browse/IVY-1429
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: unspecified, master
>         Environment: windows
>            Reporter: Greg Creager
>
> Currently the ivy report mechanism does not show 'branch' info, not having this vital information makes it very hard to see what went into a build when you have the same version on a different branch.
> example:
> compA branch="proto" revision="1.0"
> compA branch="integration" revision="1.0"
> Looking at the report for two products that use these components you get only the info on revision and module, not the branch (the key factor).
> compA revision 1.0 (which 1.0 was pulled? proto or integration?
> Adding 'branch' to the report information just makes sense as it is a major factor when deciding what to pull.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)