On 01/15/09 12:14, Craig L Russell wrote:
> If there are two artifacts with the same id and different contents,
> then there is a complete abuse of the maven repository concept.
>
> Only -SNAPSHOT artifacts should ever change while keeping the same
> version number.
>
> There should be no need to "sync" repositories to change artifacts
> once they are published. The only reason to "sync" repositories should
> be to change -SNAPSHOT artifacts or add new artifacts.
+1. I completely agree.
-hg
>
> Perhaps I misunderstand.
>
> Craig
>
> On Jan 15, 2009, at 11:16 AM, Jane Young wrote:
>
>> Hi,
>>
>> 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?
>>
>> Thanks,
>> Jane
>>
>>
>>
>> Jane Young wrote:
>>> Hi Alexey,
>>>
>>> I think there is an issue with Grizzly 1.9.4 but I can't figure out
>>> where the issue is.
>>> With a fresh build from the trunk, all the remote commands fail with
>>> the message:
>>>
>>> Error encountered when making remote call: Status: 404
>>>
>>> server.log does not display anything useful.
>>>
>>> I download the bits from Hudson but it seems to be working. Can you
>>> take a look by building a fresh build from the trunk?
>>> Several people have reported this issue. I'm also seeing the same
>>> issue.
>>> Can you take a look at your earliest convenience?
>>>
>>> Thanks,
>>> Jane
>>>
>>>> Today we've integrated Grizzly 1.9.3 [svn rev. 24270], which is
>>>> OSGi compliant, and made changes to related modules to depend
>>>> directly on Grizzly artifacts.
>>>> I've built Glassfish and run QL tests, they were fine, but if you
>>>> see any issue with specific module - please let me know.
>>>>
>>>> Thanks.
>>>>
>>>> WBR,
>>>> Alexey.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell_at_sun.com
> P.S. A good JDO? O, Gasp!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>