ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Anderson <eander...@palantirtech.com>
Subject Re: branch usage
Date Mon, 08 Feb 2010 23:38:42 GMT
As per the other email, if the branch could be used with latest.integration along with a branch
then ivyde picking appropriate substitutions would work out.
_________________________________________________________
Eric Anderson
Palantir Technologies | Engineering Team Lead
eanderson@palantirtech.com | 520.440.3773
_________________________________________________________

On Feb 5, 2010, at 5:59 AM, Juha Ranta wrote:

> 
> 
> 
> Luke Renn wrote:
>> 
>> On Thu, Feb 4, 2010 at 12:38 PM, Matt Benson <gudnabrsam@gmail.com> wrote:
>>> All:  Does any documentation exist of any depth concerning the use of
>>> branch
>>> attributes among Ivy files?
>> 
>> There's not much to them.  One thing (iirc) is that you need to change
>> the repository patterns if you're using branches.
>> 
>> ivy.<whatever>.default.artifact.pattern=[organisation]/[module]/([branch]/)[revision]/[type]s/[artifact].[ext]
>> ivy.<whatever>.default.ivy.pattern=[organisation]/[module]/([branch]/)[revision]/[type]s/[artifact].[ext]
>> 
>> Otherwise a publish of two versions on different branches will blow
>> the other one away.
>> 
> 
> I also use the branch attribute in my patterns, but despite this, I think
> it's a good idea to always have different revisions for each release even
> across the branches. IIRC, there are some Ivy functions which don't work
> well if you have the same revision in different branches. 
> 
> About branches, they're useful in that you can get the latest.* revision
> from a given branch. For instance,
> 
> <dependency name="mymod" org="myorg" branch="release_1"
> rev="latest.integration"/>
> 
> etc. 
> 
> 
> -- 
> View this message in context: http://old.nabble.com/branch-usage-tp27456726p27468139.html
> Sent from the ivy-user mailing list archive at Nabble.com.
> 


Mime
View raw message