I am just trying buidr and it looks really nice, especially after 2 days of fighting with some old maven bugs.
And as first step in learning buildr I would like to add a small patch. It is concerning HTTP_PROXY env variable.
A lot of programs use this variable as a default proxy url. For example RubyGems. So I no need to pass any options to this program. Also I expect that other programs would use the variable. And I mean build here.
Of course we could do Buildr.options.proxy.http = ENV['HTTP_PROXY']
but we are talking about reducing amount of work for developer. Aren't we?
So here is a patch (also without the patch test are fail for me).
> I am just trying buidr and it looks really nice, especially after 2 > days of fighting with some old maven bugs.
> And as first step in learning buildr I would like to add a small > patch. It is concerning HTTP_PROXY env variable.
> A lot of programs use this variable as a default proxy url. For > example RubyGems. So I no need to pass any options to this program. > Also I expect that other programs would use the variable. And I mean > build here.
> Of course we could do > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> but we are talking about reducing amount of work for developer. Aren't > we?
> So here is a patch (also without the patch test are fail for me).
And for accessing internal repos you have not to use proxy. It mean that we need to configure proxy per-repository, or at least swith off proxy for some repos. Something like this
> On 7/5/07, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> > Hi.
> > I am just trying buidr and it looks really nice, especially after 2 > > days of fighting with some old maven bugs.
> > And as first step in learning buildr I would like to add a small > > patch. It is concerning HTTP_PROXY env variable.
> > A lot of programs use this variable as a default proxy url. For > > example RubyGems. So I no need to pass any options to this program. > > Also I expect that other programs would use the variable. And I mean > > build here.
> > Of course we could do > > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> > but we are talking about reducing amount of work for developer. Aren't > > we?
> > So here is a patch (also without the patch test are fail for me).
> And for accessing internal repos you have not to use proxy. It mean > that we need to configure proxy per-repository, or at least swith off > proxy for some repos. Something like this
> On 5 июл, 22:45, "Assaf Arkin" <a...@labnotes.org> wrote:
> > Thanks, I'm adding this to 1.2.
> > Assaf
> > On 7/5/07, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> > > Hi.
> > > I am just trying buidr and it looks really nice, especially after 2 > > > days of fighting with some old maven bugs.
> > > And as first step in learning buildr I would like to add a small > > > patch. It is concerning HTTP_PROXY env variable.
> > > A lot of programs use this variable as a default proxy url. For > > > example RubyGems. So I no need to pass any options to this program. > > > Also I expect that other programs would use the variable. And I mean > > > build here.
> > > Of course we could do > > > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> > > but we are talking about reducing amount of work for developer. Aren't > > > we?
On 7/10/07, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> Another option is setup list of excluded addresses, like maven does. I > even like it more.
> Configuration would look like
> options.proxy.skip_hosts << "internal-server.mycompany.com" #skip by > adress > options.proxy.skip_hosts << /10\.192\.33\.\d+/ #or by regexp that > matched non-proxied addresses
I think exclusion is a better idea. That way, you just worry about the list of repositories for each project, and can specify all the exclusions in one place (e.g. your home directory buildr.rb file).
We can use glob patterns, so *.mycompany.com will exclude all hosts in the domain.
Assaf
On Jul 10, 7:37 am, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> > And for accessing internal repos you have not to use proxy. It mean > > that we need to configure proxy per-repository, or at least swith off > > proxy for some repos. Something like this
> > On 5 июл, 22:45, "Assaf Arkin" <a...@labnotes.org> wrote:
> > > Thanks, I'm adding this to 1.2.
> > > Assaf
> > > On 7/5/07, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> > > > Hi.
> > > > I am just trying buidr and it looks really nice, especially after 2 > > > > days of fighting with some old maven bugs.
> > > > And as first step in learning buildr I would like to add a small > > > > patch. It is concerning HTTP_PROXY env variable.
> > > > A lot of programs use this variable as a default proxy url. For > > > > example RubyGems. So I no need to pass any options to this program. > > > > Also I expect that other programs would use the variable. And I mean > > > > build here.
> > > > Of course we could do > > > > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> > > > but we are talking about reducing amount of work for developer. > Aren't > > > > we?
> > And for accessing internal repos you have not to use proxy. It mean > > that we need to configure proxy per-repository, or at least swith off > > proxy for some repos. Something like this
> > On 5 июл, 22:45, "Assaf Arkin" <a...@labnotes.org> wrote:
> > > Thanks, I'm adding this to 1.2.
> > > Assaf
> > > On 7/5/07, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> > > > Hi.
> > > > I am just trying buidr and it looks really nice, especially after 2 > > > > days of fighting with some old maven bugs.
> > > > And as first step in learning buildr I would like to add a small > > > > patch. It is concerning HTTP_PROXY env variable.
> > > > A lot of programs use this variable as a default proxy url. For > > > > example RubyGems. So I no need to pass any options to this program. > > > > Also I expect that other programs would use the variable. And I mean
> > > > build here.
> > > > Of course we could do > > > > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> > > > but we are talking about reducing amount of work for developer. > Aren't > > > > we?
> > > And for accessing internal repos you have not to use proxy. It mean > > > that we need to configure proxy per-repository, or at least swith off > > > proxy for some repos. Something like this
> > > > On 7/5/07, Anatol Pomozov <anatol.pomo...@gmail.com> wrote:
> > > > > Hi.
> > > > > I am just trying buidr and it looks really nice, especially after 2 > > > > > days of fighting with some old maven bugs.
> > > > > And as first step in learning buildr I would like to add a small > > > > > patch. It is concerning HTTP_PROXY env variable.
> > > > > A lot of programs use this variable as a default proxy url. For > > > > > example RubyGems. So I no need to pass any options to this program. > > > > > Also I expect that other programs would use the variable. And I mean
> > > > > build here.
> > > > > Of course we could do > > > > > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> > > > > but we are talking about reducing amount of work for developer. > > Aren't > > > > > we?
> > > > And for accessing internal repos you have not to use proxy. It mean > > > > that we need to configure proxy per-repository, or at least swith > off > > > > proxy for some repos. Something like this
> > > > > > I am just trying buidr and it looks really nice, especially > after 2 > > > > > > days of fighting with some old maven bugs.
> > > > > > And as first step in learning buildr I would like to add a small > > > > > > patch. It is concerning HTTP_PROXY env variable.
> > > > > > A lot of programs use this variable as a default proxy url. For > > > > > > example RubyGems. So I no need to pass any options to this > program. > > > > > > Also I expect that other programs would use the variable. And I > mean
> > > > > > build here.
> > > > > > Of course we could do > > > > > > Buildr.options.proxy.http = ENV['HTTP_PROXY']
> > > > > > but we are talking about reducing amount of work for developer. > > > Aren't > > > > > > we?