IVY-1143 created for this thread and linked to IVYDE-134. A rough patch is
attached.
Jon
On Tue, Nov 24, 2009 at 7:32 AM, Jon Schneider wrote:
> > -
>
> > So Solr might be the easiest way of achieving an Ivy indexer.
>
>> Probably. As a side note, whi
> -
> So Solr might be the easiest way of achieving an Ivy indexer.
> Probably. As a side note, while thinking of installing a server side
> component to provide search, I started to wonder why not use a
> repository manager in that case. During devoxx I
2009/11/21 Nicolas Lalevée :
>
> Le 19 nov. 2009 à 12:06, Xavier Hanin a écrit :
>
>> I really like the idea to use a solr instance colocated with the repository.
>> I've seen a presentation on solr yesterday at devoxx, and it sounds like so
>> close to what we need. The only problem I see with it
Le 19 nov. 2009 à 12:06, Xavier Hanin a écrit :
> I really like the idea to use a solr instance colocated with the repository.
> I've seen a presentation on solr yesterday at devoxx, and it sounds like so
> close to what we need. The only problem I see with it is that it requires to
> install a s
Le 18 nov. 2009 à 20:17, Jon Schneider a écrit :
> While I digest Nicolas' novel :) (thanks for the additional insight on
> Lucene by the way), I will suggest one other idea.
>
> We could allow for the option of a Solr instance collocated with the
> repository on one machine to serve up the inde
I really like the idea to use a solr instance colocated with the repository.
I've seen a presentation on solr yesterday at devoxx, and it sounds like so
close to what we need. The only problem I see with it is that it requires to
install a server side component, getting closer to what repository ma
While I digest Nicolas' novel :) (thanks for the additional insight on
Lucene by the way), I will suggest one other idea.
We could allow for the option of a Solr instance collocated with the
repository on one machine to serve up the index stored on the repository.
IvyDE could be configured by the
On Tuesday 17 November 2009 16:55:21 Jon Schneider wrote:
> > When you say "anywhere you choose", is it limited to a location on the
> > filesystem? Or do you intend to make use of ivy repositories
>
> access/publish
>
> > mechanism to store the index remotely? With filesystem only the usage
> > so
2009/11/17 Jon Schneider
>
> > If the index grows, accessing the index from a remote box may become
> long.
> > If you think big, you will have to find a way to transfer index updates
> to
> > the clients which is optimizing the network, such as transferring diffs
> or
> > something similar. But
> When you say "anywhere you choose", is it limited to a location on the
> filesystem? Or do you intend to make use of ivy repositories
access/publish
> mechanism to store the index remotely? With filesystem only the usage
> sounds rather limited. With ivy repository mechanism you can store your
>
On Tuesday 17 November 2009 15:18:13 Xavier Hanin wrote:
> 2009/11/16 Jon Schneider
>
> > On Sat, Nov 14, 2009 at 9:42 AM, Xavier Hanin >
> > >wrote:
> > >
> > > One thing I'm not sure to fully understand: it seems that you plan to
> >
> > store
> >
> > > the index on the client (say the develope
2009/11/16 Jon Schneider
> On Sat, Nov 14, 2009 at 9:42 AM, Xavier Hanin >wrote:
>
> > One thing I'm not sure to fully understand: it seems that you plan to
> store
> > the index on the client (say the developer's box), according to your
> > example
> > with dir="${ivy.settings.dir}/index". But
On Sat, Nov 14, 2009 at 9:42 AM, Xavier Hanin wrote:
> One thing I'm not sure to fully understand: it seems that you plan to store
> the index on the client (say the developer's box), according to your
> example
> with dir="${ivy.settings.dir}/index". But it also seems like every client
> will hav
2009/11/14 Jon Schneider
> That is exactly right. It is also the first step in two of my other future
> goals:
>
> 1. Unused dependency analysis. I realize this won't ever be perfect since
> there is no limit to the way dependencies can be used (sometimes
> exclusively) in specific metadata li
One thing I'm not sure to fully understand: it seems that you plan to store
the index on the client (say the developer's box), according to your example
with dir="${ivy.settings.dir}/index". But it also seems like every client
will have the responsibility to maintain the index, is that right? Sound
That is exactly right. It is also the first step in two of my other future
goals:
1. Unused dependency analysis. I realize this won't ever be perfect since
there is no limit to the way dependencies can be used (sometimes
exclusively) in specific metadata like Spring context files, but
neverthel
On Friday 13 November 2009 10:24:56 Gilles Scokart wrote:
> Seems nice. But I'm not sure I understand what it will be used for.
> What would be the user interface to read the index ?
The use case is pretty simple: I work on a project with no dependency. Then I
know that there some cool stuff in
Seems nice. But I'm not sure I understand what it will be used for.
What would be the user interface to read the index ?
Gilles Scokart
2009/11/11 Jon Schneider
> I've been thinking about IVYDE-134 (Quick Search feature for dependencies
> in
> repositories) and related IVY-866. If we add sup
Le 11 nov. 2009 à 16:21, Jon Schneider a écrit :
> I've been thinking about IVYDE-134 (Quick Search feature for dependencies in
> repositories) and related IVY-866. If we add support for the Nexus Indexer
> (which would be nice in its own right), we would still be lacking this
> feature for Ivy r
19 matches
Mail list logo
