That sounds like a good plan, and I
think it is very doable. As long as the other eclipse's are static (no
plugin changes), this approach should work well.
You can also do a distributed search
across all the indexes, so you don't need to maintain a merged index. Here
some info (some sequence diagrams for how to do it) : http://home.clara.net/markharwood/lucene/
If you have control over how the other
eclipse instances are installed, you can get everything for free:
- install all the documentation plugins
in each eclipse as a product extension (using the .link files)
- install your master eclipse by having
a .link file pointing to all the other documentation extensions.
- when you search from the master eclipse,
the index of all plugins will be installed (it may take some time :-),
but then you don't have to write any code.
Erik Hennum <ehennum@xxxxxxxxxx> Sent by: platform-help-dev-admin@xxxxxxxxxxx
10/28/2003 10:08 PM
Please respond to
a single searchable Lucene index from multiple Eclipse instances?
Hi, Inventive Help Developers:
Assume that I have a number of documentation plugins spread across several
Eclipse instances. Each plugin ID is unique across all of the Eclipse
So now I want a federated search across my Eclipse instances. That
want to run a search against all of my Eclipse instances and to be able
open a match in the appropriate Eclipse instance.
It looks like I can write a very simple Java application that executes
org.apache.lucene.index.IndexWriter.addIndexes() to merge the indexes from
the Eclipse instances to create one large index. If the application
harvests a mapping of plugin IDs to Eclipse instances, the application
could then construct a URL for a matched topic in the appropriate Eclipse
Based on the Eclipse use of Lucene, does that approach seem plausible and
Thanks in advance for any insights,
ehennum AT us DOT ibm DOT com
platform-help-dev mailing list