Salut,
Jane Young wrote:
> Hi Jeanfrancois,
>
> I have a question. Why are you directly deploying to java.net?
I wasn't aware we have alternative :-)
As we
> all know that java.net is slow and unstable.
Because our community/developers are outside the firewall :-) Anything
private will not works for them, unfortunately.
> Can we deploy to an internal maven repo and then rsync the artifacts to
> the repo at java.net.
> For GF artifacts, it's first deployed to rator.sfbay and then a Hudson
> job mirrors the repo to java.net.
I like that :-) At least for us it should be a safer approach.
Thanks
-- Jeanfrancois
>
> Thanks,
> Jane
>
>
> Jeanfrancois Arcand wrote:
>>
>>
>> Harsha Godugu wrote:
>>> On 01/15/09 13:02, Jeanfrancois Arcand wrote:
>>>>> Think it's correct. The reason I didn't bumped new version, because
>>>>> when I deploy Grizzly artifacts to maven, very often I see problem
>>>>> with java.net, when it reports, that connection could not be
>>>>> established.
>>>>
>>>> Got the same doing:
>>>>
>>>>> altDeploymentRepository = null
>>>>> Uploading:
>>>>> java-net:/maven2-repository/trunk/www/repository//trunk/www/repository/com/sun/grizzly/samples/grizzly-comet-chat-iframe/1.9.4/grizzly-comet-chat-iframe-1.9.4.war
>>>>>
>>>>> [INFO] Retrieving previous metadata from java.net-m2-repository
>>>>> [INFO] Uploading repository metadata for: 'artifact
>>>>> com.sun.grizzly.samples:grizzly-comet-chat-iframe'
>>>>> [INFO] Uploading project information for grizzly-comet-chat-iframe
>>>>> 1.9.4
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] Error installing artifact's metadata: Error while deploying
>>>>> metadata: Connection failed: Unable to connect to
>>>>> https://svn.dev.java.net/svn/maven2-repository/trunk/www/repository/
>>>>>
>>>>> svn: The specified baseline is not the latest baseline, so it may
>>>>> not be checked out.
>>>>> svn: CHECKOUT of '/svn/maven2-repository/!svn/bln/269968': 409
>>>>> Conflict (https://svn.dev.java.net)
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] For more information, run Maven with the -e switch
>>> May be Jane / Terena could help Grizzly jars get published?
>>
>> Actually after many retry it eventually works. But that's painful to
>> upload up to 6 times the jars just because of this exception. Now
>> 1.9.4 was finally uploaded :-)
>>
>> A+
>>
>> -- Jeanfrancois
>>
>>
>>>
>>> thanks...
>>> (ps:i will be off line for 2Hrs from now)
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>