[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-help-dev] Multiple product Help Search Indices.
|
Thanks, I wasn't sure if maybe it resided relative to the config
files,being in the workspace is fine. We don't want to share workspaces
between different configurations either :-).
Thanks,
-----------------------------------
Peter Manahan
WebSphere Tools
Build/Install and
Product Architecture
------------------------------------
manahan@xxxxxxxxxx
Vlad
Klicnik/Toronto/IBM@IBMCA To: platform-help-dev@xxxxxxxxxxx
Sent by: cc:
platform-help-dev-admin@e Subject: Re: [platform-help-dev] Multiple product Help Search
clipse.org Indices.
18/04/2002 08:37 AM
Please respond to
platform-help-dev
There were some follow-up question to this posted to platform-update-dev
... specifically where is the platform "state location". This area is
always in the metadata associated with each workspace. So it will always
reflect the help contributions to the specific running Eclipse instance
that is using the workspace. If you share (serially) the same workspace
with two different eclipse configurations (ie. eclipse instances with
different plugin mix) the help support will work, but you are forcing the
index files to be repeatedly updated to match the plugin mix on each use of
the different eclipse configurations. In any case, I would not recommend
sharing workspaces between different Eclipse configurations for this, and
lots of other reasons.
Dorian
Birsan/Toronto/IBM@IBMCA To:
Sent by: platform-help-dev@xxxxxxxxxxx
platform-help-dev-admin@e cc:
clipse.org Subject: Re:
[platform-help-dev] Multiple product Help
Search Indices.
04/17/2002 03:30 PM
Please respond to
platform-help-dev
When help starts, it calls the platform to collect all the plugins that
contribute documentation. I don't know how configurations work, but I
suppose that only the plugins in the current configuration are returned, so
help navigation is built out of those plugins.
Indexing is done on a first invocation of search, so only documents defined
by the current navigation are indexed. On subsequent eclipse sessions,
plugin changes are detected and the index is updated accordingly.
The index is stored in the help state location, as returned by the
platform. If each configuration has its own state location, then there is
no issue. If the plugin state locations are shared among all
configurations, then you end up with one index, so there is no
configuration specific index.
Do you know if each configuration uses its own plugin state location?
-dorian