dev@glassfish.java.net

Re: Stop repackaging Grizzly to support OSGi

From: Harsha Godugu <Harsha.Godugu_at_Sun.COM>
Date: Thu, 15 Jan 2009 13:13:34 -0800

On 01/15/09 12:53, Oleksiy Stashok wrote:
> Hi Harsha,
>
>>>
>>> There is a typo in my first e-mail. It should be Grizzly 1.9.3.
>>> The culprit is that grizzly-utils-1.9.3.jar artifact on Nexus
>>> repository
>>> (http://maven.glassfish.org/content/repositories/java.net2/com/sun/grizzly/grizzly-utils/1.9.3/)
>>> is not sync'd with the maven repository on
>>> http://download.java.net/maven/2/com/sun/grizzly/grizzly-utils/1.9.3.
>>>
>>> The one on java.net has 17Jan while the one in Nexus repository has
>>> 07Jan and the jar size is different as well.
>>> If you manually download the artifact from java.net and replace the
>>> one in your local repo that should fix the problem.
>>> Or remove Nexus repo from pom.xml.
>>>
>>> Harsha, do you know why Nexus repo is not sync'd with download.java.net?
>> Simple.. Alexey didn't bump up the version when he integrated
>> Grizzly 1.9.3 . Is that correct Alexey? (The fact that 1.9.3
>> grizzly-utils jar existed before 13th Jan tells me that. ).Nexus
>> fetches artifacts only once and caches them. If there is already one
>> available with same version, in the cache, it would get the same old
>> unless a dependent made a request for the next version of the
>> artifact/jar/resource.
> 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. And I can not be sure, if all or half of Grizzly modules
> were deployed.
> So when I started to deploy Grizzly 1.9.3, it failed, meantime I made
> additional "last fixes" and keep redeploying the artifacts until
> succeeded. Unfortunately grizzly-utils was successfully deployed first
> time, which I didn't expect. The update you see (13th Jan) I did
> yesterday, just hoped that it will force maven to synchronize local
> and global repositories.
>
> Today we've integrated version 1.9.4, which will should fix that maven
> conflict.
Ok. Thanks Alexey!


-hg
>
> Thanks.
>
> WBR,
> Alexey.
>
>>