On 8/27/07, bhatia <[EMAIL PROTECTED]> wrote: > > > 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
These demos are not on the Ivy website... but maybe you've found a link from Ivy website? I thought I had removed it though, since it's also a demo of a commercial product. I also want to publish a modified project in the local repository; I guess > that can be done with Cruise Control. No, CruiseControl does not publish to a local repository (by local I mean on the developer workstation). It publishes to an integration repository. But how do I tell Ivy, that it should > resolve from the local repository and not from the network repository ? It's because the local repository is the first in a chain where return first is set to true. I think you can get details on this in the default settings tutorial, and the multi-project example. Xavier. 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 <[EMAIL PROTECTED]> 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. > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
