On 10/5/11 11:32 AM, Bill Shannon wrote:
> Fortunately, git is in the Solaris 11 package repository.
>
> Unfortunately, it doesn't seem to be working. Do I need to do something
> special to teach it about the http proxy?
>
> $ git clone git://java.net/grizzly~git grizzly
> Cloning into grizzly...
> java.net[0: 192.9.164.103]: errno=Connection timed out
> fatal: unable to connect a socket (Connection timed out)
Try: /git/config --global/http/./proxy/[hostname:port]
>
>
> Ryan Lubke wrote on 10/04/11 09:49:
>> On 10/3/11 6:49 PM, Bill Shannon wrote:
>>> git!?! Grrrrrrrrrrrrrrrrrreat. :-(
>>>
>>> cause I haven't wasted enough time fooling around with development
>>> tools today...
>>>
>>> Where are the instructions for how to get git for Mac OS and Solaris,
>>> and how to use it to check out grizzly?
>> http://git-scm.com/
>>
>> While the site has a Mac dmg, you'll probably have to build it for
>> Solaris.
>>
>> Once you have it installed, you can issue:
>>
>> git clone git://java.net/grizzly~git
>>
>>
>>>
>>> Oleksiy Stashok wrote on 10/03/2011 04:37 PM:
>>>> Hi Bill,
>>>>
>>>> the latest Grizzly should be checked out using git:
>>>>
>>>> git clone git://java.net/grizzly~git
>>>>
>>>> WBR,
>>>> Alexey.
>>>>
>>>>
>>>> On 10/03/2011 02:43 PM, Bill Shannon wrote:
>>>>> I'm trying to build the latest grizzly on my Mac (just checked
>>>>> out, empty
>>>>> Maven repository).
>>>>>
>>>>> If I build with just "mvn", it fails in one of the tests.
>>>>>
>>>>> If I build without running the tests, it fails with the following.
>>>>> What could I be doing wrong?
>>>>>
>>>>>
>>>>>
>>>>> [INFO] Failed to resolve artifact.
>>>>>
>>>>> Missing:
>>>>> ----------
>>>>> 1) com.sun.grizzly:grizzly-framework:test-jar:tests:1.9.35-SNAPSHOT
>>>>>
>>>>> Try downloading the file manually from the project website.
>>>>>
>>>>> Then, install it using the command:
>>>>> mvn install:install-file -DgroupId=com.sun.grizzly
>>>>> -DartifactId=grizzly-framework -Dversion=1.9.35-SNAPSHOT
>>>>> -Dclassifier=tests
>>>>> -Dpackaging=test-jar -Dfile=/path/to/file
>>>>>
>>>>> Alternatively, if you host your own repository you can deploy the
>>>>> file there:
>>>>> mvn deploy:deploy-file -DgroupId=com.sun.grizzly
>>>>> -DartifactId=grizzly-framework -Dversion=1.9.35-SNAPSHOT
>>>>> -Dclassifier=tests
>>>>> -Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url]
>>>>> -DrepositoryId=[id]
>>>>>
>>>>> Path to dependency:
>>>>> 1) com.sun.grizzly:grizzly-portunif:jar:1.9.35-SNAPSHOT
>>>>> 2) com.sun.grizzly:grizzly-framework:test-jar:tests:1.9.35-SNAPSHOT
>>>>>
>>>>> ----------
>>>>> 1 required artifact is missing.
>>>>>
>>>>> for artifact:
>>>>> com.sun.grizzly:grizzly-portunif:jar:1.9.35-SNAPSHOT
>>>>>
>>>>> from the specified remote repositories:
>>>>> central (http://repo1.maven.org/maven2),
>>>>> codehaus (http://repository.codehaus.org),
>>>>> java.net (http://download.java.net/maven/2),
>>>>> glassfish-maven2-repository.dev.java.net
>>>>> (http://download.java.net/maven/glassfish/)
>>>>
>>>
>>
>