I think Brian Fox answered this partly on the users list, (Archiva
uses an older version of the indexer and a newer version of lucene,
which creates an invalid index for nexus or m2e)
I wanted to add that index is only used for searching, and is not used
at all when an artifact is requested from a remote repository.
On Jun 9, 2009, at 10:41 AM, Allan Ditzel wrote:
> Hi all,
>
> I've posted to the user list, but I'm not sure whether that list is
> the best for this question. We're running into a situation where we
> are proxying a remote repo, which has an index, and we're telling
> our nexus install to use remote indexes for this repo. However, when
> we try to access anything from the remote repo (it's the atlassian
> public repo), such as an archetype from the command-line we see an
> error telling us it can't find the specified artifact. What's
> interesting is that when we tail the nexus log, if we force a re-
> index of that repo, nexus throws an error saying it couldn't find an
> index.
>
> Is there any way to get more logging information? We already have
> the debug log level set to DEBUG for nexus.
>
> Thanks,
>
> Allan
---------------------------------------------------------------------
To unsubscribe, e-mail:
nexus-dev-unsubscribe@...
For additional commands, e-mail:
nexus-dev-help@...
