What I do is have an ivy settings file on a file share somewhere (put it with your ivy repository), then each developer has their own ivy setting file that they put have locally on their machine, that includes the shared ivy settings file. The ivy-settings file on the location machines should include the one stored in your repository using either an http address, or a mapped drive possibly using an environment variable.
On 10/11/07, Loehr, Ruel < [EMAIL PROTECTED]> wrote: > > I'm trying to setup my projects such that: > > 1) I can check out into eclipse after setting up ivyde > 2) Resolve my classpath > > And have everything work with very little user configuration. > > My current snag is with setting the user preferences. Say I have 5 > projects (a,b,c,d,e) and each one has a settings file, > ./settings/org.jayasoft.ivyde.eclipse.prefs > > #Thu Oct 11 09:11:32 CDT 2007 > acceptedTypes=[inherited] > eclipse.preferences.version=1 > instance/org.eclipse.core.net/org.eclipse.core.net.hasMigrated=true > ivy_conf_path=file\:/C\:/eclipse33/eclipse/workspace/snm-trunk/config/iv > y/ivyconf.xml > javadocTypes=[inherited] > retreive.pattern=none > sourceTypes=[inherited] > > Is there any way to not have the ivy_conf_path hardcoded to an absolute > value? This file gets checked into source control and developers have > there eclipse location in different areas. I've tried making it a > relative path, but no luck. > > > > > > -- Regards, John Gill
