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 lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <12343634.post@talk.nabble.com>
Date: Mon, 27 Aug 2007 02:00:57 -0700 (PDT)
From: bhatia <Bhatia@OFAC.CH>
To: ivy-user@incubator.apache.org
Subject: Re: ivy demo with cruise control
In-Reply-To: <635a05060708270142h6e98cca8p971bd196de4f227c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <12342770.post@talk.nabble.com>
 <635a05060708270142h6e98cca8p971bd196de4f227c@mail.gmail.com>


I was referring to the following tutorial on the Ivy website:
http://demos.worldofjava.org/fullstack-demo.htm
http://demos.worldofjava.org/fullstack-demo.htm 

I also want to publish a modified project in the local repository; I guess
that can be done with Cruise Control. But how do I tell Ivy, that it should
resolve from the local repository and not from the network repository ?

For example, in your demo (URL mentioned above), you do a resolve on the
File project and that gets you the dependency from the local repository (the
List project on which you made changes). How do you do that ?

thanks


Xavier Hanin wrote:
> 
> 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/
> 
> 

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