Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: error (nike.apache.org: local policy)
Message-ID: <521CD6E0.7050505@gmx.us>
Date: Tue, 27 Aug 2013 09:42:08 -0700
From: Edwin Castro <0ptikGhost@gmx.us>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ivy-user@ant.apache.org
Subject: Re: latest.integration is not resolving to the latest revision
References: <5217FD31.2050400@gmx.us>
 <CAC_SY71OqFK3x7mK_KY4n1tA4DWnH4c_i+N-hJMPuOszUn=GdA@mail.gmail.com>
 <521B7E22.4080000@gmx.us>
 <CAC_SY70bfg9sXb7p68R2r17eM6s=YYC7Sh5wuyR5TdA7a4C03g@mail.gmail.com>
In-Reply-To: 
 <CAC_SY70bfg9sXb7p68R2r17eM6s=YYC7Sh5wuyR5TdA7a4C03g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 8/27/13 2:29 AM, Mark Thornton wrote:
> Just that, what gets printed to the console.
>
>
> On Monday, 26 August 2013, Edwin Castro <0ptikGhost@gmx.us> wrote:
>
>> On 8/24/13 4:42 AM, Mark Thornton wrote:
>>> Also check the log from ivy.
>> What do you mean by "log from ivy"?
>>
>> I was unaware of any "log" information other than what gets printed to
>> the console when it runs via Ant.

Thanks. The console output wasn't helping me much other than telling me
the specific revision getting resolved but not why. :-(

I was able to figure out my problem by inspecting the published ivy.xml
files in the respository. I was previously unaware that dynamic
revisions are resolved during the deliver phase so that the revisions in
the published ivy.xml are fixed.

A --> B --> C --> D

I was trying to build module A which has transitive dependency for
module B using rev="latest.integration" and so on down the dependency
chain. For some reason, module D was rebuilt and published but module C
was not rebuilt (not an issue with ivy, I suspect some odd queue symptom
in Jenkins). Thus whenever module A got all its dependencies it picked
up a fixed revision of D which was not new enough. All I needed to do
was rebuild/publish module C which correctly triggered module B to
rebuild/publish and so on.

--
Edwin G. Castro