Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: James Davis <james.davis@atsid.com>
To: "ivy-user@ant.apache.org" <ivy-user@ant.apache.org>
Date: Wed, 4 Aug 2010 09:39:20 -0700
Subject: RE: Any advice / documention on how to use branches in Ivy?
Thread-Topic: Any advice / documention on how to use branches in Ivy?
Thread-Index: Acsz695J9lZU/YVkRI+mzmqnWyZYigAB1GOA
Message-ID: 
 <7E9646C605F85F45B9FEA87EF1F29C123A3A448DB6@diamondhead.apptechsys.com>
References: <14FE3FC4CE1CFE4FB31C3D05A6D678B7AE5C09@exceu1.ofchouten.nl.rw>
 <FC28BDC007C04141969BD4EAAFEC60F1287E65AADC@NP1EXMB012.corp.halliburton.com>,<B16CF07A-0077-4752-B502-F8525BA1A9F8@palantir.com>
 <7E9646C605F85F45B9FEA87EF1F29C123A3A332DF0@diamondhead.apptechsys.com>
 <6C078FBA-EBC7-4071-AC27-601B28D7ED6C@palantir.com>
In-Reply-To: <6C078FBA-EBC7-4071-AC27-601B28D7ED6C@palantir.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_7E9646C605F85F45B9FEA87EF1F29C123A3A448DB6diamondheadap_"
MIME-Version: 1.0

--_000_7E9646C605F85F45B9FEA87EF1F29C123A3A448DB6diamondheadap_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

If you have different versions for each build, then you wouldn't have a pro=
blem with artifact collisions.  However, it would be difficult to tell whic=
h version of the artifact came from which branch.  A resolve on an ivy.xml =
with a dependency on  a specific branch would not be locked down to just th=
at branch, and could bring in versions that were not published on that bran=
ch (at least this is my understanding of how ivy works due to how the patte=
rns work).

James Davis * QA Engineer II/Software Engineer
Applied Technical Systems, Inc. * Information Engineering
web: www.atsid.com * e-mail: james.davis@atsid.com
(p) 360.698.7100 x241 * (f) 360.698.7200

From: Eric Anderson [mailto:eanderson@palantir.com]
Sent: Wednesday, August 04, 2010 8:44 AM
To: ivy-user@ant.apache.org
Subject: Re: Any advice / documention on how to use branches in Ivy?

We publish each artifact with a unique version per build so we wouldn't get=
 colliding in that sense. So if Ivy checks the ivy.xml file to make sure it=
s the right branch, then we would be okay?
_________________________________________________________
Eric Anderson
Palantir Technologies | Engineering Team Lead
eanderson@palantir.com<mailto:eanderson@palantirtech.com> | 520.440.3773
_________________________________________________________

On Aug 4, 2010, at 8:26 AM, James Davis wrote:


If you don't change the artifact pattern, your artifacts will collide with =
each other.  One thing that we have done is make the branch optional in the=
 pattern.

An example of an optional branch identifier in the previous example would b=
e [module]/([branch])/[revision]/[type]/[artifact](.[ext]).  If there branc=
h is specified, it will be used, if not it will be ignored in the pattern.


James Davis * QA Engineer II/Software Engineer
Applied Technical Systems, Inc. * Systems Division
web: www.atsid.com<http://www.atsid.com> * e-mail: james.davis@atsid.com<ma=
ilto:james.davis@atsid.com>
(p) 360.698.7100 x241 * (f) 360.698.7200

________________________________________
From: Eric Anderson [eanderson@palantir.com]
Sent: Tuesday, August 03, 2010 3:18 PM
To: ivy-user@ant.apache.org<mailto:ivy-user@ant.apache.org>
Subject: Re: Any advice / documention on how to use branches in Ivy?

Im really interested in using the branch attribute but not interested in ch=
anging my artifact pattern.

What problems did you hit by not changing it?
_________________________________________________________
Eric Anderson
Palantir Technologies | Engineering Team Lead
eanderson@palantir.com<mailto:eanderson@palantirtech.com>
_________________________________________________________

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:Phillip.Rhodes@redwood.com]
Sent: Tuesday, July 27, 2010 10:46 AM
To: ivy-user@ant.apache.org<mailto:ivy-user@ant.apache.org>
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 pri=
vileged information for the sole use of the intended recipient.  Any review=
, use, distribution, or disclosure by others is strictly prohibited.  If yo=
u are not the intended recipient (or authorized to receive information for =
the intended recipient), please contact the sender by reply e-mail and dele=
te all copies of this message.


--_000_7E9646C605F85F45B9FEA87EF1F29C123A3A448DB6diamondheadap_--