You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Shawn Castrianni <Sh...@halliburton.com> on 2008/02/04 17:37:02 UTC

missing branch attribute in resolved ivy file

I have several different modules each with their own independent branching schemes.  I have setup module specific settings in my settings file to specify which branch of which module to use.  The problem is in the published modules ivy files.  These resolved ivy files do not specify which branch of which module was used in the dependency section.  It just lists the name and revision of each dependent module.  I want to know which branch was used for each dependent module.

I guess my question is why doesn't the deliver task populate the branch attribute for dependencies in the resolved ivy files?  How would someone be able to trace back the history of a given module build without knowing which branch the dependencies came from?

---
Shawn Castrianni
CM Lead Architect
Landmark
Halliburton Drilling, Evaluation and Digital Solutions Building 2
2101 City West Blvd.
Houston, TX  77042
Work:  713-839-3086
Cell:  832-654-0888
Fax:  713-839-2758

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

Re: missing branch attribute in resolved ivy file

Posted by Xavier Hanin <xa...@gmail.com>.
On Feb 4, 2008 5:37 PM, Shawn Castrianni <Sh...@halliburton.com>
wrote:

> I have several different modules each with their own independent branching
> schemes.  I have setup module specific settings in my settings file to
> specify which branch of which module to use.  The problem is in the
> published modules ivy files.  These resolved ivy files do not specify which
> branch of which module was used in the dependency section.  It just lists
> the name and revision of each dependent module.  I want to know which branch
> was used for each dependent module.
>
> I guess my question is why doesn't the deliver task populate the branch
> attribute for dependencies in the resolved ivy files?  How would someone be
> able to trace back the history of a given module build without knowing which
> branch the dependencies came from?

I guess the answer is that we simply forgot this case. I think it really
makes sense to populate the branch as soon as it's not the default one (I
mean Ivy default). You can open a bug in JIRA.

Xavier


>
> ---
> Shawn Castrianni
> CM Lead Architect
> Landmark
> Halliburton Drilling, Evaluation and Digital Solutions Building 2
> 2101 City West Blvd.
> Houston, TX  77042
> Work:  713-839-3086
> Cell:  832-654-0888
> Fax:  713-839-2758
>
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and
> privileged information for the sole use of the intended recipient.  Any
> review, use, distribution, or disclosure by others is strictly prohibited.
>  If you are not the intended recipient (or authorized to receive information
> for the intended recipient), please contact the sender by reply e-mail and
> delete all copies of this message.




-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/