ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Oulds <jonat...@sbdev.net>
Subject Re: buildnumber Ant task & automated updates of ivy.xml
Date Fri, 21 Nov 2008 16:32:27 GMT
np, I though it was probably me getting the wrong end of the stick

Mitch Gitman wrote:
> Oh no, I wasn't referring to anything you were doing, Jonathan. I was making
> a general point, and really going back to what I was wanting to do in my
> original post: to modify the /ivy-module/info@revision attribute in the
> ivy.xml file *in project source*. When you get right down to it, I should *not
> *even be wanting to do this.
> 
> On Fri, Nov 21, 2008 at 2:26 AM, Jonathan Oulds <jonathan@sbdev.net> wrote:
> 
>> ...
>> I think either I am misunderstanding you or t'other way around, we are not
>> storing the ivy revision number under SVN except as part of the tag name
>> created by CI on a successful build.  The ivy file we have under SVN does
>> not contain it's own revision, this is only inserted into the delivered ivy
>> file and is derived from the latest build number in the ivy repository.
>>
>>
>>
>>> As I alluded in the lengthy post I sent earlier today, it's becoming
>>> apparent to me that your project source proper is not the ideal place to
>>> be
>>> keeping track of the current Ivy version of that project. It's like Ivy
>>> does
>>> not want to be used in this way. Not only do you have to keep track of the
>>> version manually through some scheme of your own, but again you have an
>>> open
>>> invitation for your current version (as recorded in project source) to get
>>> out of sync with the latest version that exists in the Ivy repository.
>>>
>>>
>>>  That didn't sound like a good idea to us, so we headed down the route of
>>>> not having the version numbers specified in the ivy file and only
>>>> resolving
>>>> the correct version number upon delivery.  Our CI machine will auto
>>>> increment the build number, when a module changes significantly we do a
>>>> special build of the module updating the major or minor version.
>>>>
>>>> long post, hope some of it is helpful
>>>> any advice / comments are welcome
>>>>
>>>>
> 


Mime
View raw message