Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 14703 invoked from network); 13 Nov 2008 14:44:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Nov 2008 14:44:41 -0000 Received: (qmail 56577 invoked by uid 500); 13 Nov 2008 14:44:48 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 56527 invoked by uid 500); 13 Nov 2008 14:44:47 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 56516 invoked by uid 99); 13 Nov 2008 14:44:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Nov 2008 06:44:47 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mgitman@gmail.com designates 74.125.78.146 as permitted sender) Received: from [74.125.78.146] (HELO ey-out-1920.google.com) (74.125.78.146) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Nov 2008 14:43:28 +0000 Received: by ey-out-1920.google.com with SMTP id 4so361786eyk.10 for ; Thu, 13 Nov 2008 06:44:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=ky/2nMyluw80a8Z2Cr3mtj10kwZ7lbyBRhaY1jIXMUk=; b=unztqpgYgb0ng8Gh8FcHFoyOisq68ZUgQluuONGYmTlqCLca6wlOGAeV57qCrzSCkU 3xcYjypDX16rLWfxFBVDwMXQLvEmKmOpz92p0M6Rf+B1x4cY+tZaAK5dXLqguSDz07l+ wxfESq03+e+GdBAgXBMI/h4JBEAMUEdBRnAvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=budYk57WHfqQVF1cRl2yGxfVJv5Z09weSP7Dawc88a8gQ+YLrG7+Q7k4loVupQFOZG 4DDdav7sILGbGbNfeXAgPvXdeDYSGkZrSz+JfZFDxVOr+HazhYYNYh4Zjisd3qc+jxGJ RRR+QCwcd/6IekbsvL5rPvR0G5utzfZvXrJ6c= Received: by 10.187.160.3 with SMTP id m3mr3346161fao.51.1226587450907; Thu, 13 Nov 2008 06:44:10 -0800 (PST) Received: by 10.187.164.14 with HTTP; Thu, 13 Nov 2008 06:44:10 -0800 (PST) Message-ID: <7916a6a60811130644r6c52c54ej17c44cc1219def5f@mail.gmail.com> Date: Thu, 13 Nov 2008 06:44:10 -0800 From: "Mitch Gitman" To: ivy-user@ant.apache.org Subject: Re: Resolver or dependency In-Reply-To: <912580.53655.qm@web33408.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24863_6575009.1226587450901" References: <912580.53655.qm@web33408.mail.mud.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_24863_6575009.1226587450901 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline If project B depends on project A, then the only knowledge B has of the latest version of A is what's in the Ivy repository that the Ivy resolver is using. When you get right down to it, the extra functionality you're looking for is really the work of a continuous integration system. The sequence would go like this: 1. You check in changes to project A to source control. 2. A CI system like Hudson detects the change to A and proceeds to build the project itself. 3. At this end of a successful build, Hudson publishes A.jar (or whatever the artifacts are) to the Ivy repository in use. 4. If you're using something like the Hudson Ivy plugin, then a change to project A will trigger a rebuild of its dependent project, B. By the way, does anyone know the current state of the Hudson Ivy plugin when it comes to Ivy 2.0? On Thu, Nov 13, 2008 at 4:49 AM, Viktor Sadovnikov wrote: > Hi everyone, > > Seems I am either making fundamental mistake in understanding Ivy or > missing > something. How should I setup compilation when I have two projects: A and > B, > the last one depends on the latest version of A. > My setup is based on "multi-project" example, which comes > with Ivy. Code of both projects is changed locally and I want to test > compilation of B. Both "compile" of B and "compile-all" fail until A is > published. I would expect something in either "dependencies" of B or > resolvers > to tell Ivy that A needs to be rebuild. > > Could anyone point me to my mistake? > > Thanks a lot, > Viktor > > > > ------=_Part_24863_6575009.1226587450901--