On 10/6/11 10:32 AM, Bill Shannon wrote:
> Ryan Lubke wrote on 10/06/2011 09:31 AM:
>>
>>>>
>>>> I tried both
>>>>
>>>> git config --global http.proxy www-proxy.us.oracle.com:80
>>>>
>>>> and
>>>>
>>>> git config --global http.proxy http://www-proxy.us.oracle.com:80/
>>>>
>>>> Neither worked.
>>>>
>>>> Don't I need to use an http: URL with git clone?
>>>>
>>>
>> It would be nice if the java.net folks configured git to export the
>> repos via
>> http/https.
>> Guess I'll log an issue for that.
>>
>> I think for now, behind the firewall, you'll need to use SSH.
>>
>> ssh://[java.net ID]@git.java.net/grizzly~git
>>
>> Make sure you've exported your keys first (done via your java.net user
>> preferences).
>
> Thanks, that worked. Actually, it "just worked"! Maybe I had already
> exported my keys previously, but I didn't have to do anything to make
> it work.
Just a friendly tip. If you don't care about the entire history of the
repository (i.e., you just want
to build it), you can include '--depth 1' in the clone arguments
(without the quotes).
This will speed up the clone process quite a bit (useful when on a slow
connection).