Bug 17223 - Eclipse SDK F1 Driver Help System Problems
Summary: Eclipse SDK F1 Driver Help System Problems
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P1 critical (vote)
Target Milestone: 2.0 F2   Edit
Assignee: Dorian Birsan CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-23 09:16 EDT by Stephen Woolley CLA
Modified: 2002-05-28 11:38 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Woolley CLA 2002-05-23 09:16:04 EDT
Hi,

I have been successfully running Eclipse (20020416) in Information Center mode 
for the last few weeks on my Web server.  When I upgraded to the latest 2.0 
stable build (F1 - 20020521), my Information Center would not work, and 
standalone help also stopped working.

I followed the updated installation instructions at:

http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-help-
home/infocenter.html

When I try to access my new F1 Eclipse help system 
(http://netquestion.hursley.ibm.com:8080/help) the following error is displayed 
in my IE window:

There was an error in your action: 
javax.servlet.ServletException: org.eclipse.core.boot.BootLoader 

I am running Tomcat 3.2 and have modified the server.xml file in the conf 
directory of Tomcat to point to the correct plugin directory.

Here's what the context entry in my server.xml file looks like:

	<Context path="/help" 
		 docBase="D:\eclipsef1\plugins\org.eclipse.help.webapp_2.0.0" >
	</Context>

Do you have any ideas as to why my information center, and standalone help has 
stopped working as a result of upgrading to F1?

Why are version numbers included in the directory names?  This is messy and I'm 
sure has caused the problems I am experiencing.  The version number is 
generally stored in plugin.xml.  Why does it need to be in two places?

Many thanks,


Steve

WebSphere MQ Information Architect
IBM United Kingdom Laboratories
Hursley Park
Winchester
UK
Comment 1 Dorian Birsan CLA 2002-05-23 10:49:32 EDT
Steve, we're in the process of testing the F1 builds and haven't got to the 
infocenter scenario. I think the problem could also be caused by changes done 
in the update manager (we need to run with the -noupdate flag and thought we 
did, but need to make sure it actually works).
I am marking it as a P1 item.
Comment 2 Dorian Birsan CLA 2002-05-23 15:50:12 EDT
You were right: the boot loader plugin has a version number and it could not be 
found.
The short term workaround is to rename the org.eclipse.core.boot_2.0.0 to 
org.eclipse.core.boot (no version).
Comment 3 Konrad Kolosowski CLA 2002-05-28 11:38:39 EDT
Fixed.