On 7/22/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi Milos,
I'm not sure about those 3 indices. Is there a reason you would separate
them as such? Currently, they are all one, so you can search across all
3 types and get a consistent ranking.
Ok, that's probably confusion on my side. There is 3 different classes
extending AbstractRepositoryIndex that's why I though there are 3
indices. I actually didn't completely get why are ther 3 different
ones, each of them filling different values..
what is the intedned usage of these RepositoryIndex classes? do they
work on top of the same index data? don't the documents created clash?
What we've done is created a full index and a minimal one (just md5,
filename, id). The latter is designed for the IDEs, and is enough to do
dependency selection. If you need to search the other info, it might be
best to manage the local repository index and just make sure the
artifacts are local first.
I'd rather have access to the complete one from the IDE. What is the
index actually mapped to class-wise (artifact/metadata/pom? repository
index) ? when experimenting i figured that I actually need to use both
Artifact and Pom RepositoryIndex, because they contain a bit different
data and sometimes I need this and sometimes that..
The index is a directory with a number of files, so you will probably
want to grab a zip. The current standard is .index and .minimal-index in
the root of the repository (but its configurable).
is the zipped index file already implemented or is it a TBD item?
what's teh name of the zip in .index folder?
The repository webapp will be responsible for maintaining the index.
That is pretty much in place now (though still needs some bugfixes and
correction of ineffeciencies).
WDYT?
cool with me
Milos
- Brett
On 22/07/2006 6:41 PM, Milos Kleint wrote:
> Hello,
>
> i've recently added maven repository indexing features to the netbeans
> maven support. I index the local repository. I query it for
> artifactsId/groupId for code-completion in pom.xml, for achetypes when
> creating new project. Will also be used for adding dependecies and
> general searching features.
>
> a natural next step is to include repome repository content as well,
> however the question is how to get it's index. One way would be
> probably to distribute the index with the netbeans modules and create
> the index manually once in a while. Of course it will be often out of
> synch.
>
> Another option is that each repository exposes the index at a
> predefined place and one could retrieve it through wagon. Then it
> would be the repository's responsibility to update the index when new
> artifacts arrive and the client code would be responsible for updating
> the local cached copy regularly.
>
> Here goes the proposal:
> let's have
> 1- .artifactIndex/ folder for the Artifact index
> 2- .pomindex/ for Pom index (it would be nice if the pom index
> contained completely resolved models with injected parent pom's
> content, for details see http://jira.codehaus.org/browse/MRM-121
> 3- .metadataIndex for indexing metata.
>
> I'm not entirely sure on the content of the folders, will zipping it
> up help for download size?
> Where would such a remote repository indexing code reside? the maven
> repository webapp?
>
> Regards
>
> Milos
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
