Im really interested in using the branch attribute but not interested in changing my artifact pattern.
What problems did you hit by not changing it? _________________________________________________________ Eric Anderson Palantir Technologies | Engineering Team Lead [email protected] _________________________________________________________ On Jul 27, 2010, at 8:49 AM, Shawn Castrianni wrote: > That is what I have done with my artifact pattern for the repository: > > [module]/[branch]/[revision]/[type]/[artifact](.[ext]) > > --- > Shawn Castrianni > > > -----Original Message----- > From: Phillip Rhodes [mailto:[email protected]] > Sent: Tuesday, July 27, 2010 10:46 AM > To: [email protected] > Subject: Any advice / documention on how to use branches in Ivy? > > I see that the <info> and <dependency> elements have a "branch" > attribute, and I can see that it sorta-kinda > > works the way I would naively expect... if I publish an artifact with > branch set to "foo" and then try to resolve > > with a dependency of the same name, but with the branch set to "bar" > then it doesn't match and the resolve > > fails. So far, so good. But my real question is how to best take > advantage of this? > > > > If I just change the branch and publish, winding up with different > revisions with different branches commingle together, things > > don't seem to work so smoothly. Is the idea that we are to make > "branch" part of the repository pattern, so that > > artifacts are segregated on a per branch basis? Or something else? > > > > Any and all advice or pointers to documentation are much appreciated. > > > > > > Thanks, > > > > Phil > > ---------------------------------------------------------------------- > 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.
smime.p7s
Description: S/MIME cryptographic signature
