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?
thanks...
(ps:i will be off line for 2Hrs from now)