Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@archiva.apache.org
Received-SPF: pass (athena.apache.org: domain of mkleint@gmail.com designates
 74.125.46.29 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ffSeSqoYa0mpgcTUefCMHrm2pKF8IX7pWUSzvayBvdHX8DXW4UXqdGvXyWzKF9hyDeWmGw17UccpZj5LiKs0rJTU5OysTBZh7+kUa+Pg7y0CI7GBGKMoIU5lstY/6+rora98ezpiRRD/PQbpON01HB+3/pNfI8c9xDtgbRLdMLI=
Message-ID: <f84708e90805260518v7f652a1fpda15a2fb7eb59769@mail.gmail.com>
Date: Mon, 26 May 2008 14:18:02 +0200
From: "Milos Kleint" <mkleint@gmail.com>
To: dev@archiva.apache.org
Subject: Re: Archiva search integration in Q4E
In-Reply-To: <1a57a2980805251725w37380c8apb24aa0ec236967e0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c44fcda20805231008g1a6e36bv20eb1b7ba7f0e665@mail.gmail.com>
	 <1a57a2980805251725w37380c8apb24aa0ec236967e0@mail.gmail.com>

Hey,

Until there's a webservice running 24/7 against central repository,
there's no need to actually consider it for IDE integration I believe.
Additionally the downloadable index can satisfy multiple requests at
once, reasonably fast from multiple repositories. That makes
aggregation of multiple repos reasonably predictable. With webservices
you end up with one server having unreliable response, being down,
unreachable etc. and everything get bogged down.
The upside is always uptodate data, but I'm not convinced it's that
important for index content. a month old central repo is more than
enough.

just my 2 cents.

Milos Kleint

PS: the netbeans maven integration is using nexus as primary indexing
engine (more are possible throung pluggable spi) just for this reason:
it has central repo index up.


On 5/26/08, Maria Odea Ching <oching@apache.org> wrote:
> Hi Mike,
>
>  Currently, Archiva doesn't have any web service for this yet but it's
>  definitely in the future roadmap (scheduled for 1.2 I think). The repository
>  index file resides by default in the repository directory, but this can be
>  overridden and the location is saved in the config file (archiva.xml). It
>  would be easier if Q4E would be able to use a web service to search the
>  Archiva index instead of having it download the index files from each
>  repository. Do you already have a set date for the next release where the
>  search feature will be included? You may also want to take a look at the
>  archiva-indexer and archiva-lucene consumers modules as these touch the
>  indexing and search part of Archiva.
>
>  Joakim also started a POC (archiva-jarinfo [1]) a couple of months ago which
>  I think can be used with Q4E, but I'm not sure how much work still needs to
>  be done here =)
>
>  Thanks,
>  Deng
>
>  [1] http://www.nabble.com/WIP-POC-archiva-jarinfo-td15974634.html
>
>
>  On Sat, May 24, 2008 at 1:08 AM, Michael Poindexter <staticsnow@gmail.com>
>  wrote:
>
>
>  > Hi,
>  >
>  > I'm one of the developers of the Q4E Eclipse plugin for integrating Maven 2
>  > with Eclipse.  One of the features we are adding in the next release is the
>  > ability to search artifacts, both in a search dialog and as autocompletion
>  > when editing a POM xml file.
>  >
>  > Currently we've developed code to support searching the central repository
>  > via the index file that is created of it, but we'd also like to support
>  > searching local repositories like Archiva, Nexus, and Artifactory.  How
>  > would you recommend for me to go about searching the artifacts in an
>  > Archiva
>  > repository?  Is there some index file we can download and use for search?
>  > Some web service we can use?
>  >
>  > Thanks in advance for any pointers!
>  >
>  > Mike Poindexter
>  >
>