> -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 17, 2004 2:52 PM > To: Avalon Developers List > Subject: Re: [magic] proxies and remote repositories > > Farr, Aaron wrote: > > Hello. > > > > I'm just in the process of committing a few changes to the reactor.xml > and > > build.xml which: > > > > 1. allow for a 'user.properties' to be set rather than having users > edit > > the default build.properties > > > Handling of user.properties is already in place. > See ContextualTask.
Okay, then we can back out my change to the avalon/build.xml > > > > 2. allow for the following properties for setting an HTTP proxy: > > project.proxy.host > > project.proxy.port > > project.proxy.user > > project.proxy.password > > > > 3. runs a <setproxy> task in the reactor.xml init target which wasn't > > being called by the build.xml init target. So I commented out the > > reactor init methods and added the setproxy. Someone else may have > > a better idea. > > Yes - the above is needed. Still working on it too. Let me know if my changes break non-proxy installs. > > Finally, do we have a way to change the remote repositories? In some > cases, > > individuals will want to point to a local mirror of ibiblio or dpml. > > Sure - take a look at the Home class and how it is pulling in > information about available repositories. > > > And did we think about using some of depot's tools for repository and > > resource management? > > It should be possible to map these in as supplimentary plugins - but > more thinking needed. Definitely. Gotta run to a meeting, but I want to look into this more. J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
