Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=PkuWEMw0dpbGK9p0AEndapL0rgZXt141vEz9nqA2T1eOh5HLev+YqQCr809TtxUY/5XfN0phoBD5TnmqM9ko071xRcXuMH4vjvI44cssiJqp/vuRf8z7Vlv1JmitQBgGNR5mUcHzPwiQQ86Xa4thcUTbffZm15nm9GBtZdt5fdA=
Message-ID: <635a05060708270142h6e98cca8p971bd196de4f227c@mail.gmail.com>
Date: Mon, 27 Aug 2007 10:42:15 +0200
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: ivy demo with cruise control
In-Reply-To: <12342770.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_21578_1774851.1188204135741"
References: <12342770.post@talk.nabble.com>

------=_Part_21578_1774851.1188204135741
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 8/27/07, bhatia <Bhatia@ofac.ch> wrote:
>
>
> Hello,
> Its a very inspiring demo. Thats exactly what I want to implement, the
> ability to find a dependency in the workspace. For example, the File
> project
> is able to resolve a modified dependency (the list project) in the local
> workspace. How does that happen ?
> I thought I would normally be required to first publish the list project
> to
> the repository with my changes and then do a resolve in the File project
> from IvyDE to get my changes in the list project.
> Can someone explain me how to do this in Ivy ? Or maybe I need
> CruiseControl
> with IvyCruise to do this trick.


I'm not sure about which demo you're referring to. With a continuous
integration server, what you can do is make the server publish each
integration build to a repository, so that a new version is available each
time someone commit. You don't need a plugin for this, all CI server can
call the target you want, and it's up to you to publish your module in your
build.xml target called by the server. If you want to get a locally modified
version, you need to publish it to a repository, but we recommend to publish
it to a local repository (on the developer workstation), so that the locally
modified version is only available to the developer. I think the tutorial on
dependent projects demonstrate this (and the multi project too, but there
isn't much doc).

Is it clearer now?

Xavier

thanks
>
> --
> View this message in context:
> http://www.nabble.com/ivy-demo-with-cruise-control-tf4333778.html#a12342770
> Sent from the ivy-user mailing list archive at Nabble.com.
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/

------=_Part_21578_1774851.1188204135741--