Eclipse Community Forums: Platform - User Assistance (UA) » Using pre-build indexes with Eclipse Help

Home » Eclipse Projects » Platform - User Assistance (UA) » Using pre-build indexes with Eclipse Help

Using pre-build indexes with Eclipse Help [message #469288]

Mon, 14 May 2007 18:04

Eclipse User

We are currently trying to use the DITA open toolkit to create eclipse
help documentation from Java Doc's. So far so good. We can create the
documentation just fine and the eclipse help system recognizes and
displays everything. However, this documentation is shared across
multiple programmers and may change frequently, so we wish to store the
plugin on a share and pre-create indexes. We've managed to build the
indexes( with command line eclipse ), but for some reason eclipse help
doesn't seem to recognize that they exist( we still get "indexing..." ).

We've actually removed all other help files so only our plugin shows up.
Eclipse still tells us that it is Indexing ... we have tried a few things
but to no avail.

Here is the structure of our plugin directory.
com.foo.bar/ doc.zip
index.xml
nl/en/doc_index.zip <--- this is the preIndex.
plugin.xml
foo-java.xml

The plugin.xml is this

<?xml version="1.0" encoding="utf-8"?>
<plugin name="Manual" id="map" version="1.0" provider-name="DITA">
<extension point="org.eclipse.help.toc">
<toc file="foo-java.xml" primary="true"/>
</extension>
<extension point="org.eclipse.help.index">
<index file="index.xml"/>
</extension>
</plugin>

So the question is... How do I get eclipse to recognize these indexes?

Thanks

Greg Honig
Advantage Consulting

Re: Using pre-build indexes with Eclipse Help [message #469300 is a reply to message #469288]

Wed, 23 May 2007 16:40

Eclipse User

Take a look at the very bottom of the following help document:

http://help.eclipse.org/help32/topic/org.eclipse.platform.do c.isv/guide/ua_help_setup_preindex.htm

Did you include "org.eclipse.help.base/productIndex=com.foo.bar" in your
plugin_customization.ini file as described?

Re: Using pre-build indexes with Eclipse Help [message #469335 is a reply to message #469300]

Tue, 29 May 2007 17:34

Eclipse User

Adam,

I've done that. I've also tried modifying the preferences.ini in the
org.eclipse.help.base.jar with the same text. Neither of these seem to
work for me.

I have been studying the instructions that you referenced over the last
several weeks and still haven't figured this out. We have been following
the "Building an index for a product" section as we are generating the
eclipsehelp plugin files via the DITA Open Toolkit.

The steps are as follows
* First generate the plugin with the DITA OpenToolkit.
* Run eclipse with the indexTool application.
* Add the plugin_customization.ini file at this point.
* Copy the plugin directory into the eclipse plugin directory.

What are we missing? New indexes are created for these no mater what we've
tried.

Thanks

Greg Honig
Advantage Consulting

Re: Using pre-build indexes with Eclipse Help [message #469342 is a reply to message #469300]

Wed, 30 May 2007 16:37

Eclipse User

If your plugin_customization.ini file is being picked up correctly and it
references the plug-in that contains the index under the format discussed
in the help document then everything should work.

I tried this out myself today and found that the pre-index is functional.
I've uploaded a sample for you to take a look at. It is available here:

http://www.eclipse.org/eclipse/platform-ua/documents/Product IndexExample.zip

To run this properly, import the two projects it contains into your
workspace and then create a new Eclipse Application launch configuration.
Make sure that the product is set to "com.example.product" on the Main
tab. To ensure that only the indexed docs are included in the launch (and
not all the Eclipse SDK docs), switch to the plug-ins tab and select
launch with "plug-ins selected below only", then deselect the Target
Platform option from the list and click the "Add Required Plug-ins"
button. Also, to ensure that any generated indexes are discarded on each
successive launch (to make sure it's working), switch to the configuration
tab and check the "clear the configuration area before launching" box.

Re: Using pre-build indexes with Eclipse Help [message #469348 is a reply to message #469342]

Wed, 30 May 2007 18:08

Eclipse User

I just discovered something odd. The pre-index isn't working for me when
running the product from the workbench as I described in the previous
post. It does work when the product is exported and run from the file
system. We may have a bug on our hands here and I will investigate that,
but it shouldn't affect your problem unless your product is being run from
the workbench.

You can still compare the configuration in the supplied sample to yours to
make sure it is correct.

Re: Using pre-build indexes with Eclipse Help [message #469354 is a reply to message #469348]

Thu, 31 May 2007 10:39

Eclipse User

Originally posted by: coynerb.ociweb.com

Thanks for the sample files. Can you help me understand why there are two
plug-ins. Listed below is some questions about our journey trying to
figure out how to tell Eclipse to utilize our pre-indexed documentation
files.

We have a single documentation plug-in that executes in a standalone
InfoCenter instance. Our current plug-in directory contains the
pre-indexed files. We are having trouble telling the InfoCenter to use our
pre-index files.

We successfully pre-index the files using the steps outlined in this
document:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse. platform.doc.isv/reference/extension-points/org_eclipse_help _contentExtension.html

We successfully start the InfoCenter using the steps outlined in this
document:
http://help.eclipse.org/help31/index.jsp?topic=/org.eclipse. platform.doc.isv/reference/misc/help_infocenter_update.html

Here is a snapshot of our plug-in directory that is copied to the Eclipse
'plugins' directory:
$ECLIPSE_HOME/
+ plugins
+ com.foo.bar
- doc.zip
+ nl
+ en
- doc_index.zip
- plugin.xml
- toc.xml
- plugin_customization.ini

Here is what the 'plugin.xml' looks like:
<plugin name="Foo Bar Docs" id="com.foo.bar" version="1.0"
provider-name="DITA">
<extension point="org.eclipse.help.toc">
<toc file="toc.xml" primary="true"/>
</extension>
</plugin>

Here is what the 'plugin_customization.ini' file looks like:
org.eclipse.help.base/productIndex=com.foo.bar

Now we run into a brick wall.

We do not explicitly reference the 'plugin_customization.ini' in the
'plugin.xml' file. Should we? If so, how do we reference this file in
'org.eclipse.help.toc' extension point? Perhaps we should have another
extension point?

The documentation outlined in the "Pre-indexing documentation" page says:
"add an index element to the org.eclipse.help.toc extension in a
documentation plug-in, to specify directory where index will exist"

Digging a little deeper we find more information:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/product_configproduct.htm

This page seems to indicate that we need another extension point:
<extension point="org.eclipse.help.index">
<index file="index.xml"/>
</extension>

Is this extention point something we need to include? If so, why and how?

Continuing to dig deeper we find more information:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/product_configproduct.htm

<extension point="org.eclipse.help.toc">
<toc file="toc1.xml" primary="true"/>
<toc file="toc2.xml" primary="true" category="myCategory"/>
<toc file="task.xml"/>
<toc file="sample.xml" extradir="samples"/>

<index path="index/"/>
</extension>

Is the 'index' element something we need to include? If so, why and how?

Perhaps we are trying to make this harder than it actually is. However, we
are unable to figure this out. Any help you can provide is greatly
appreciated. It would be very beneficial to know what we should see (or
not see) when the InfoCenter successfully utilizes our pre-indexed files.
Currently we are seeing Eclipse store the indexed files under
'$ECLIPSE_HOME/configuration/org.eclipse.help.base'. If the pre-indexing
works should we see any output here?

Thanks in advance. We are hoping for a "one-line" configuration change. :-)
Brian

Re: Using pre-build indexes with Eclipse Help [message #469360 is a reply to message #469354]

Thu, 31 May 2007 15:29

Eclipse User

Okay, I think what's happening is that your "plugin_customization.ini"
file isn't being read or used. There are two ways that eclipse can be
pointed at a specific "plugin_customization.ini" file.

One way, which is much less common, is to launch eclipse as follows:
"eclipse -pluginCustomization <path>/plugin_customization.ini". This is
very simple, but unfortunately you cannot use it in your case. This is
because when starting in infocenter mode you are not invoking eclipse
directly. You are actually calling a Java class
(org.eclipse.help.standalone.Infocenter) which will, in turn, launch
eclipse for you. Therefore, there is no way for you to specify a command
line argument to the eclipse launcher.

So you will have to use the second method of pointing at a
"plugin_customization.ini" file which is to create your own eclipse based
product. This is done by use of the "org.eclipse.core.runtime.product"
extension point. For more information on defining an Eclipse based product
with an extension point see the following help doc:

http://help.eclipse.org/help32/topic/org.eclipse.platform.do c.isv/guide/product_def_extpt.htm

In the extension point for your product you will point at the
"plugin_customization.ini" file using a property called
"preferenceCustomization".

Since your "plugin_customization.ini" file is in the same directory as
your "plugin.xml", your "plugin.xml" should look like this (or similar):

<plugin name="Foo Bar Docs" id="com.foo.bar" version="1.0"
provider-name="DITA">
<extension id="docs" name="Foo Bar Docs Product"
point="org.eclipse.core.runtime.products">
<product
application="org.eclipse.ui.ide.workbench"
description="Foo Bar Docs"
name="Foo Bar Docs Product">
<property name="preferenceCustomization"
value="plugin_customization.ini" />
<property name="appName" value="Foo Bar Docs Product" />
</product>
</extension>
<extension point="org.eclipse.help.toc">
<toc file="toc.xml" primary="true"/>
</extension>
</plugin>

Note: the application referenced by your product does not matter since you
will only ever launch your product in infocenter mode.
"org.eclipse.ui.ide.workbench" is the application used by the eclipse SDK.

Once your plugin.xml defines a product, eclipse needs to know that it
should run your product when it launches (as opposed to
"org.eclipse.sdk.ide"). This is specified in
"<eclipse_home>/configuration/config.ini" under a parameter labelled
"eclipse.product". You should change yours to point at "com.foo.bar.docs"
if you use the product id from my example above
("eclipse.product=<plugin_id>.<product_id>" where the product id is
specified in the "org.eclipse.core.runtime.products" extension point).

So in your case:
- The single plug-in should:
- contain all your docs and your preindex
- contain your plugin_configuration.ini at the plug-in root
- specify your product id which references your plugin_customization.ini
file
- the config.ini in your eclipse home directory should:
- have a line that reads "eclipse.product=<plugin_id>.<product_id>"
- have no other line with "eclipse.product"

Note that if you drop this into a regular Eclipse SDK all the default docs
will be there as well. You may want to remove the doc plug-ins
(org.eclipse.jdt.doc.user, org.eclipse.jdt.doc.isv,
org.eclipse.pde.doc.user, org.eclipse.platform.doc.user,
org.eclipse.platform.doc.isv).

For more information on working with products I suggest reading through
the entire help section from the link referenced above. In addition you
can run through a PDE cheat sheet that shows you how to export products as
eclipse applications. This can be found in the Eclipse SDK by going to:
"Help > Cheat Sheets... > Plug-in Development > Creating a Rich Client
Application".

Some additional notes:

Index means a couple different things in help. There are search indexes
and keyword indexes. Your preindex is a search index. The
"org.eclipse.help.index" extension point you were talking about is for
keyword indexes.

Furthermore, there are two types of prebuilt search indexes, product wide
indexes in which all your documentation is indexed in one place, and
per-plugin indexes in which each doc plugin provides preindexes for it's
own docs. The index that you are trying to create is a product wide index.
The "index" element that can be included on the "org.eclipse.help.toc"
extension point is used to specify the location of a plugin index. Thus,
you do not need to worry about that.

Indexing is only performed once per install (unless doc plugins are
updated or the index is determined to be stale), even across multiple
workspaces. The index, once it's generated is stored under
"<eclipse_home>/configuration/org.eclipse.help.base/". When you perform a
search, the first thing the help system does is look here for an index and
if one is found, make sure it is up to date. After that it will look to
see if you have a product preindex and if it finds one it will copy it
into the directory above. So yes, you should see your index files in that
directory after your first launch even if your preindex is being used
correctly.

Hope this helps.

Re: Using pre-build indexes with Eclipse Help [message #469363 is a reply to message #469360]

Thu, 31 May 2007 15:51

Eclipse User

Adam Archer wrote:

> One way, which is much less common, is to launch eclipse as follows:
> "eclipse -pluginCustomization <path>/plugin_customization.ini". This is
> very simple, but unfortunately you cannot use it in your case. This is
> because when starting in infocenter mode you are not invoking eclipse
> directly. You are actually calling a Java class
> (org.eclipse.help.standalone.Infocenter) which will, in turn, launch
> eclipse for you. Therefore, there is no way for you to specify a command
> line argument to the eclipse launcher.

I just discovered that you can actually pass this argument on your
infocenter call and it will get passed on to the eclipse launcher. So your
call to start the infocenter would look something like this if you wanted
to take this shortcut:

java -classpath
d:\eclipse\plugins\org.eclipse.help.base_3.3.0.v20070523.jar
org.eclipse.help.standalone.Infocenter -command start -eclipsehome
d:\eclipse -port 8081 -pluginCustomization
d:\eclipse\plugin_customization.ini

Re: Using pre-build indexes with Eclipse Help [message #469370 is a reply to message #469363]

Thu, 31 May 2007 17:41

Eclipse User

Originally posted by: coynerb.ociweb.com

Thanks for the quick reply.

I updated the files with your recommended changes but Eclipse appears to
still generate the index files. Here is how I came to this conclusion:

Step 1)
- updated my documentation plug-in configuration files with your updates

Step 2) Modified The Generated Index
- extracted the 'nl/en/doc_index.zip'
- modified the 'indexed_*' files to include my name in a comment (# BRIAN)
- added a new file called 'brian.txt'
- zipped up the changes

The goal here is to see if Eclipse actually finds and extracts my
plug-in's 'doc_index.zip' file (it does).

Step 3)
- The '$ECLIPSE_HOME/contributions/org.eclipse.help.base' directory is
empty.

Step 3)
- Started the InfoCenter with the '-pluginCustomization' option pointing
to my plug-in's 'plugin_customization.ini' file

I actually started the InfoCenter with and without this option and
observed no apparent difference.

Step 4)
- Executed a search

Eclipse pauses a bit and displays a message stating that it is performing
an index.

Step 5)
- Eclipse appears to have found my 'doc_index.zip' file because the
'$ECLIPSE_HOME/contributions/org.eclipse.help.base' directory contains the
'brian.txt' file. However, none of the 'indexed_*' files contain the
comment I added (# BRIAN)... see step 2 above. The timestamps on the files
are different too. This leads me to believe that Eclipse is finding my
pre-indexed zip file but decides to re-generate the index.

After determining that Eclipse is extracting the contents of the
'doc_index.zip' I decided to remove your recommended changes (putting my
plug-in's files back to their original state). What is interesting is that
Eclipse still finds my plug-in's 'doc_index.zip' file. I assume this
because the 'brian.txt' continues to be copied to the
'$ECLIPSE_HOME/contributions/org.eclipse.help.base'.

I must be missing a fundamental concept with regards to the help system
and how pre-indexing is suppose to work. When will I know that Eclipse is
actually utilizing the pre-indexed files? Is there something that will or
will not happen when it starts working. Is there a way to turn on logging
and see more information about what the help system is doing?

Thanks again for your time.
Brian

Re: Using pre-build indexes with Eclipse Help [message #469393 is a reply to message #469370]

Fri, 01 June 2007 15:24

Eclipse User

This is getting too difficult to discuss via a newsgroup. I'd like to take
a look at your actual sample.

Can you please open a bug against Platform/User Assistance and upload your
sample?

Re: Using pre-build indexes with Eclipse Help [message #471442 is a reply to message #469288]

Thu, 10 January 2008 13:05

Eclipse User

This is a multi-part message in MIME format.
--------------010404020508040607020104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I just tried to work with pre-built indexes myself and found the
documentation hard to follow. I've updated the document to add more
details - the new help page is attached.

--------------010404020508040607020104
Content-Type: text/html; charset=ISO-8859-1;
name="ua_help_setup_preindex.htm"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="ua_help_setup_preindex.htm"

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBU cmFuc2l0aW9u
YWwvL0VOIj4NCjxodG1sPg0KPGhlYWQ+DQo8bWV0YSBuYW1lPSJjb3B5cmln aHQiIGNvbnRl
bnQ9IkNvcHlyaWdodCAoYykgSUJNIENvcnBvcmF0aW9uIGFuZCBvdGhlcnMg MjAwMCwgMjAw
Ni4gVGhpcyBwYWdlIGlzIG1hZGUgYXZhaWxhYmxlIHVuZGVyIGxpY2Vuc2Uu IEZvciBmdWxs
IGRldGFpbHMgc2VlIHRoZSBMRUdBTCBpbiB0aGUgZG9jdW1lbnRhdGlvbiBi b29rIHRoYXQg
Y29udGFpbnMgdGhpcyBwYWdlLiIgPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29u dGVudC1UeXBl
IiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9SVNPLTg4NTktMSI+DQo8 bWV0YSBodHRw
LWVxdWl2PSJDb250ZW50LVN0eWxlLVR5cGUiIGNvbnRlbnQ9InRleHQvY3Nz Ij4NCjxsaW5r
IHJlbD0iU1RZTEVTSEVFVCIgaHJlZj0iLi4vYm9vay5jc3MiIGNoYXJzZXQ9 IklTTy04ODU5
LTEiIHR5cGU9InRleHQvY3NzIj4NCjxzY3JpcHQgbGFuZ3VhZ2U9IkphdmFT Y3JpcHQiIHNy
Yz0iUExVR0lOU19ST09UL29yZy5lY2xpcHNlLmhlbHAvbGl2ZWhlbHAuanMi Pjwvc2NyaXB0
Pg0KPHRpdGxlPlByZS1pbmRleGluZyBkb2N1bWVudGF0aW9uPC90aXRsZT4N CjwvaGVhZD4N
Cjxib2R5Pg0KDQo8aDI+UHJlLWluZGV4aW5nIGRvY3VtZW50YXRpb248L2gy Pg0KDQo8cD5X
aGVuIHVzZXIgc2VhcmNoZXMgaGVscCBjb250ZW50cyBvZiBhIHByb2R1Y3Qs IHRoZSBzZWFy
Y2ggaXMgcGVyZm9ybWVkDQp3aXRoaW4gYSBkb2N1bWVudGF0aW9uIGluZGV4 LiAmbmJzcDtC
eSBkZWZhdWx0LCB0aGlzIGluZGV4ICZuYnNwO2lzIGNyZWF0ZWQNCm9uIHRo ZSBmaXJzdCBp
bnZvY2F0aW9uIG9mIGhlbHAgc2VhcmNoLCBidXQgY2FuIGJlIHByZS1idWls dCBhbmQgZGVs
aXZlcmVkDQp0byB0aGUgdXNlciB3aXRoIGVhY2ggcGx1Zy1pbiwgc2luY2Ug My4xLCBvciBh
cyBhIGNvbXBsZXRlIGluZGV4IGZvciBhIHByb2R1Y3QuICZuYnNwO1RoaXMN CnByZXZlbnRz
DQppbmRleGluZw0KZnJvbQ0Kb2NjdXJyaW5nDQpvbg0KdGhlIHVzZXIgbWFj aGluZSBhbmQg
bGV0cyB0aGUgdXNlciBvYnRhaW4gZmlyc3Qgc2VhcmNoIHJlc3VsdHMgZmFz dGVyLjwvcD4N
Cg0KPGgzPkJ1aWxkaW5nIGEgZG9jdW1lbnRhdGlvbiBpbmRleCBmb3IgYSBw bHVnLWluLjwv
aDM+DQoNCjxwPlRvIGJ1aWxkIGFuIGluZGV4IGZvbGxvdyB0aGUgc3RlcHM6 PC9wPg0KPHVs
Pg0KICA8bGk+YWRkIGFuIDxjb2RlPmluZGV4PC9jb2RlPiBlbGVtZW50IHRv IHRoZSA8Y29k
ZT5vcmcuZWNsaXBzZS5oZWxwLnRvYw0KICAgICAgZXh0ZW5zaW9uPC9jb2Rl PiBpbiBhIGRv
Y3VtZW50YXRpb24gcGx1Zy1pbiwgdG8gc3BlY2lmeSBkaXJlY3Rvcnkgd2hl cmUNCiAgICAg
IGluZGV4IHdpbGwgZXhpc3QsIGZvciBleGFtcGxlIA0KICA8cHJlPiZsdDtl eHRlbnNpb24N
CiAgICAgIHBvaW50PSZxdW90O29yZy5lY2xpcHNlLmhlbHAudG9jJnF1b3Q7 Jmd0Ow0KICAg
Jmx0O2luZGV4DQogICAgICAgICBwYXRoPSZxdW90O2luZGV4JnF1b3Q7Jmd0 Ow0KICAgJmx0
Oy9pbmRleCZndDsNCiZsdDsvZXh0ZW5zaW9uJmd0OzwvcHJlPg0KICA8L2xp Pg0KICA8bGk+
QWRkIHRoZSA8Y29kZT5oZWxwLmJ1aWxkSGVscEluZGV4PC9jb2RlPiBBTlQg dGFzayB0byB0
aGUgYnVpbGQueG1sIGZpbGUgaW4gDQogIHRoZSBwbHVnaW4gcHJvamVjdCBi eSBhZGRpbmcg
dGhlIGxpbmVzIGJlbG93LiBBIGJ1aWxkLnhtbCBmaWxlIGNhbiBiZSBjcmVh dGVkIA0KICBi
eSByaWdodCBjbGlua2luZyBvbiBNQU5JRkVTVC5NRiBpbiB0aGUgcGFja2Fn ZSBleHBsb3Jl
ciBhbmQgc2VsZWN0aW5nIHRoZSANCiAgbWVudSBpdGVtIFBERSBUb29scy9D cmVhdGUgQW50
IEJ1aWxkIEZpbGUuIFRoaXMgZXhhbXBsZSBidWlsZCB0aGUgaW5kZXggZm9y IA0KICB0aGUg
ZGVmYXVsdCBsb2NhbGUgYW5kIGFsc28gZm9yICZxdW90O25sL2ZyJnF1b3Q7 LiBUaGlzIHNo
b3VsZCBiZSBtb2RpZmllZCB0byBtYXRjaCB0aGUgDQogIGxvY2FsZXMgd2hp Y2ggeW91IGFy
ZSB1c2luZy48cHJlPiZsdDt0YXJnZXQgbmFtZT0mcXVvdDtidWlsZC5pbmRl eCZxdW90OyBk
ZXNjcmlwdGlvbj0mcXVvdDtCdWlsZHMgc2VhcmNoIGluZGV4IGZvciB0aGUg cGx1Zy1pbjog
b3JnLmVjbGlwc2UucGxhdGZvcm0uZG9jLnVzZXIuJnF1b3Q7IGlmPSZxdW90 O2VjbGlwc2Uu
cnVubmluZyZxdW90OyZndDsNCiAgICAgJmx0O2hlbHAuYnVpbGRIZWxwSW5k ZXggbWFuaWZl
c3Q9JnF1b3Q7cGx1Z2luLnhtbCZxdW90OyBkZXN0aW5hdGlvbj0mcXVvdDsu JnF1b3Q7LyZn
dDsNCiAgICAgJmx0O2hlbHAuYnVpbGRIZWxwSW5kZXggbWFuaWZlc3Q9JnF1 b3Q7cGx1Z2lu
LnhtbCZxdW90OyBkZXN0aW5hdGlvbj0mcXVvdDtubC9mciZxdW90Oy8mZ3Q7 DQombHQ7L3Rh
cmdldCZndDs8L3ByZT4NCjwvbGk+DQogIDxsaT5jcmVhdGUgYW4gaW5kZXgg YnkgYnVpbGRp
bmcgdGhlIHRhcmdldCAmcXVvdDtidWlsZC5pbmRleCZxdW90Oy4gVGhlIGFu dCB0YXNrIG11
c3QgYmUgDQogIHJ1biBpbiB0aGUgc2FtZSBKUkUgYXMgdGhlIHdvcmtzcGFj ZS4gVG8gZG8g
dGhpcyByaWdodCBjbGljayBvbiBidWlsZC54bWwsIA0KICBzZWxlY3QgdGhl IG1lbnUgaXRl
bSBSdW4gQXMvQW50IGJ1aWxkLi4uIHRoZSBhbnQgZGlhbG9nIHdpbGwgYXBw ZWFyLiBPbiB0
aGUgDQogIHRhcmdldHMgdGFiIGNoZWNrIG9ubHkgJnF1b3Q7YnVpbGQuaW5k ZXgmcXVvdDsg
YW5kIG9uIHRoZSBKUkUgdGFiIHNlbGVjdCB0aGUgcmFkaW8gDQogIGJ1dHRv biAmcXVvdDtS
dW4gaW4gdGhlIHNhbWUgSlJFIGFzIHRoZSB3b3Jrc3BhY2UmcXVvdDsuIFdo ZW4geW91IGhp
dCB0aGUgDQogICZxdW90O1J1biZxdW90OyBidXR0b24gdGhlIGluZGV4ZXMg d2lsbCBiZSBi
dWlsdC48YnI+DQo8L2xpPg0KPC91bD4NCg0KPGgzPkJ1aWxkaW5nIGFuIGlu ZGV4IGZvciBh
IHByb2R1Y3Q8L2gzPg0KDQo8cD5QZXItcHJvZHVjdCBpbmRleCBpcyBhIG9u ZSBhZ2dyZWdh
dGUgaW5kZXggb2YgYWxsIGRvY3VtZW50YXRpb24gaW4gdGhlIHByb2R1Y3Qu DQogIEl0IHNo
b3VsZCBiZSB1c2VkIGluIHNjZW5hcmlvcyBpbiB3aGljaCB0aGUgc2V0IG9m IGRvY3VtZW50
YXRpb24gcGx1Zy1pbnMgaXMNCiAgbm90IGNoYW5naW5nLiBGb3IgZXhhbXBs ZSBhbiBpbmZv
LWNlbnRlciBpbnN0YWxsYXRpb24gd2lsbCBiZW5lZml0DQogIGZyb20gcGVy LXByb2R1Y3QN
CiAgaW5kZXguPC9wPg0KPHA+VG8gYnVpbGQgYW4gaW5kZXggZm9sbG93IHRo ZSBzdGVwczo8
YnI+DQo8L3A+DQo8dWw+DQogIDxsaT5idWlsZCBhIHByb2R1Y3QsIGluY2x1 ZGluZyBhbGwg
ZG9jdW1lbnRhdGlvbiBwbHVnLWlucyw8L2xpPg0KICA8bGk+Y3JlYXRlIGFu IGluZGV4IGZv
ciBhIGRlc2lyZWQgbG9jYWxlIGJ5IHJ1bm5pbmcgdGhpcyBjb21tYW5kOiAg ICAgDQogICAg
ICAgICAgICAgICAgICAgICAgICAgIA0KICAgIDxwcmU+ZWNsaXBzZSAtbm9z cGxhc2ggLWFw
cGxpY2F0aW9uIG9yZy5lY2xpcHNlLmhlbHAuYmFzZS5pbmRleFRvb2wgLXZt YXJncyAtRGlu
ZGV4T3V0cHV0PTxpPm91dHB1dERpcmVjdG9yeTwvaT4gLURpbmRleExvY2Fs ZT08aT5sb2Nh
bGU8L2k+PC9wcmU+DQpmcm9tIHRoZSBkaXJlY3RvcnkgY29udGFpbmluZyB0 aGUgcHJvZHVj
dC4gJm5ic3A7VGhlIGZvbGxvd2luZyBhcmd1bWVudHMNCm5lZWQgdG8gYmUg c2V0IDo8YnI+
DQogICAgPGI+b3V0cHV0RGlyZWN0b3J5PC9iPiAtIHNwZWNpZmllcyBwYXRo IG9mIHRoZSBk
aXJlY3Rvcnkgd2hlcmUgdGhlIGluZGV4DQppcyB0byBiZSBzYXZlZDxicj4N CiAgICA8Yj5s
b2NhbGU8L2I+IC0gc3BlY2lmaWVzIGxvY2FsZSBmb3Igd2hpY2ggdGhlIGlu ZGV4IHdpbGwg
YmUgYnVpbHQ8YnI+DQogIDwvbGk+DQo8L3VsPg0KPHA+Rm9yIGV4YW1wbGUs IHJ1bm5pbmc8
YnI+DQo8L3A+DQo8cHJlPmVjbGlwc2UgLW5vc3BsYXNoIC1hcHBsaWNhdGlv biBvcmcuZWNs
aXBzZS5oZWxwLmJhc2UuaW5kZXhUb29sIC12bWFyZ3MgLURpbmRleE91dHB1 dD1kOi9idWls
ZC9jb20ubXkucGx1Z2luIC1EaW5kZXhMb2NhbGU9ZW48L3ByZT4NCjxwPndp bGwgcmVzdWx0
IGluIGZpbGUgPGI+ZG9jX2luZGV4LnppcDwvYj4gYmVpbmcgc2F2ZWQgaW4g dGhlIDxiPm5s
L2VuPC9iPg0KZGlyZWN0b3J5IHRoYXQgd2lsbCBiZSBjcmVhdGVkIHVuZGVy IDxiPmQ6L2J1
aWxkL2NvbS5teS5wbHVnaW48L2I+LiAmbmJzcDtUaGUNCnppcCB3aWxsIGNv bnRhaW4gaW5k
ZXggb2YgY29udGVudHMgb2YgZG9jdW1lbnRzIHRoYXQgYXJlIGF2YWlsYWJs ZSB0byB1c2Vy
cw0Kd2hlbiB0aGV5IHJ1biB0aGUgcHJvZHVjdCBpbiB0aGUgPGI+ZW48L2I+ IGxvY2FsZS48
YnI+DQo8L3A+DQoNCjxoMz5QYWNrYWdpbmcgYW5kIEluc3RhbGxhdGlvbiBv ZiB0aGUgcHJv
ZHVjdCdzIHByZS1idWlsdCBpbmRleDwvaDM+DQoNClByZS1idWlsdCBpbmRp Y2VzLCB0aGUg
PGI+ZG9jX2luZGV4LnppcDwvYj4gZmlsZXMsIG5lZWQgdG8gYmUgcGFja2Fn ZWQgYXMNCmEg
cGx1Zy1pbi4gJm5ic3A7IFlvdSBjYW4gY2hvb3NlIHRvIHVzZSBhIHBsdWct aW4gYXNzb2Np
YXRlZCB3aXRoIHRoZSBwcmltYXJ5DQpmZWF0dXJlLCBvciBjaG9vc2UgdG8g cGFja2FnZSB0
aGUgaW5kZXggZm9yIGVhY2ggbGFuZ3VhZ2UgaW50byBzZXBhcmF0ZSBmcmFn bWVudHMuPGJy
Pg0KPGJyPg0KRm9yIGV4YW1wbGUsIGlmIHByb2R1Y3QncyBkb2N1bWVudGF0 aW9uIGlzIGF2
YWlsYWJsZSBpbiB0aHJlZSBsYW5ndWFnZXMsIHNheQ0KRW5nbGlzaCwgR2Vy bWFuIGFuZCBT
aW1wbGlmaWVkIENoaW5lc2UsIGEgcGx1Zy1pbiBjb20ubXkucGx1Z2luIGNh biBoYXZlIHRo
ZSBmb2xsb3dpbmcgc3RydWN0dXJlOjxicj4NCjxwcmU+Y29tLm15LnBsdWdp bi88YnI+ICAg
ICAgICAgICAgICBwbHVnaW4ueG1sPGJyPiAgICAgICAgICAgICAgbmwvPGJy PiAgICAgICAg
ICAgICAgICAgZGUvPGJyPiAgICAgICAgICAgICAgICAgICAgZG9jX2luZGV4 LnppcDxicj4g
ICAgICAgICAgICAgICAgIGVuLzxicj4gICAgICAgICAgICAgICAgICAgIGRv Y19pbmRleC56
aXA8YnI+ICAgICAgICAgICAgICAgICB6aC88YnI+ICAgICAgICAgICAgICAg ICAgICBDTi88
YnI+ICAgICAgICAgICAgICAgICAgICAgICBkb2NfaW5kZXguemlwPGJyPiAg ICAgICAgICAg
ICAgb3RoZXIgZmlsZXMgb2YgdGhpcyBwbHVnaW48L3ByZT4NCjxicj4NCiBU aGUgSUQgb2Yg
dGhlIHBsdWctaW4gbmVlZHMgdG8gYmUgc3BlY2lmaWVkIGFzIGEgPGI+cHJv ZHVjdEluZGV4
PC9iPiBwcmVmZXJlbmNlDQpmb3Igb3JnLmVjbGlwc2UuaGVscC5iYXNlIHBs dWctaW4uJm5i
c3A7Rm9yIHBsdWctaW4gaW4gdGhlIGFib3ZlIGV4YW1wbGUsIHRoZQ0KcGx1 Z2luX2N1c3Rv
bWl6YXRpb24uaW5pDQpmaWxlIG5lZWRzIHRvIGNvbnRhaW4gdGhlIGVudHJ5 PGJyPg0KPHBy
ZT5vcmcuZWNsaXBzZS5oZWxwLmJhc2UvcHJvZHVjdEluZGV4PWNvbS5teS5w bHVnaW48YnI+
PC9wcmU+DQoNCjwvYm9keT4NCjwvaHRtbD4=
--------------010404020508040607020104--

Re: Using pre-build indexes with Eclipse Help [message #560346 is a reply to message #469288]

Wed, 23 May 2007 16:40

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560373 is a reply to message #469300]

Tue, 29 May 2007 17:34

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560383 is a reply to message #469300]

Wed, 30 May 2007 16:37

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560389 is a reply to message #469342]

Wed, 30 May 2007 18:08

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560396 is a reply to message #469348]

Thu, 31 May 2007 10:39

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560398 is a reply to message #469354]

Thu, 31 May 2007 15:29

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560404 is a reply to message #469360]

Thu, 31 May 2007 15:51

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #560411 is a reply to message #469363]

Thu, 31 May 2007 17:41

Eclipse User

Re: Using pre-build indexes with Eclipse Help [message #571298 is a reply to message #469370]

Fri, 01 June 2007 15:24

Eclipse User

This is getting too difficult to discuss via a newsgroup. I'd like to take
a look at your actual sample.

Can you please open a bug against Platform/User Assistance and upload your
sample?

Re: Using pre-build indexes with Eclipse Help [message #606360 is a reply to message #469288]

Thu, 10 January 2008 13:05

Eclipse User

Previous Topic:	Intro problems: NPE and referenced part does not exist yet
Next Topic:	Index not found when installed via Update Manager

Goto Forum:

-=] Back to Top [=-

Current Time: Tue May 20 03:03:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter