dev@grizzly.java.net

Re: build howto

From: Scott Oaks <Scott.Oaks_at_Sun.COM>
Date: Tue, 26 May 2009 11:40:24 -0400

I am running on Solaris 11, so perhaps that is an issue with the tests.
But I did a brand-new checkout this morning, so I don't know why I (and
Carlos) are seeing the dependency issue if Justin isn't.

-Scott

On 05/26/09 11:32, Jeanfrancois Arcand wrote:
> Salut,
>
> Scott Oaks wrote:
>> On 05/26/09 10:37, Jeanfrancois Arcand wrote:
>>> Salut,
>>>
>>> Scott Oaks wrote:
>>>> Is there a build howto anywhere? I found a tutorial about building
>>>> in NetBeans, but I'm looking for command-line steps.
>>>
>>> Hey hey nice to see you here :-)
>>>
>>>>
>>>> I tried just running mvn in grizzly/trunk/code/code but get an
>>>> unresolved dependency (org.jvnet.wagon-svn:wagon-svn:jar:1.8)
>>>
>>> So you checked out the code and did:
>>>
>>> % grizzly/trunk
>>> % mvn clean install
>>>
>>> and it failed? It seems the repository for java.net is broken (as
>>> usual with java.net). Can you cut& paste the stack trace?
>>
>> It's not a stack trace, but I get an error about the dependency:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> ----------
>> 1) org.jvnet.wagon-svn:wagon-svn:jar:1.8
>> ...
>>
>> Following Carlos' suggestion, I commented out the dependency, and it
>> makes grizzly-utils, but then hangs while testing it -- whichever test
>> is run after com.sun.grizzly.BaseSelectionKeyHandlerTest hangs. Or
>> maybe it's that test; I can't quite follow the output:
>> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.703
>> sec
>> Running com.sun.grizzly.BaseSelectionKeyHandlerTest
>>
>> which implies that it has just started that test, but then the other
>> output implies that test has run because the Tests run: comes before
>> the Running.
>>
>> That's the last thing I see. And of course if I kill the test, maven
>> fails so I never go on to make the other modules that I need.
>
> Hum which OS are you running? Anyway just do mvn -Dmaven.test.skip=true
> for now. I will work on reproducing the issue.
>
> Thanks!
>
> -- Jeanfrancois
>
>
>>
>> -Scott
>>
>>>
>>> Thanks!
>>>
>>> -- Jeanfarcnois
>>>
>>>
>>>>
>>>> -Scott
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>