Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313429

Summary: F1 help not displaying for the Timeouts section of the server editor.
Product: [WebTools] WTP ServerTools Reporter: Larina Cheung <larinac>
Component: wst.serverAssignee: Angel Vera <arvera>
Status: RESOLVED FIXED QA Contact: Angel Vera <arvera>
Severity: normal    
Priority: P3 CC: david_williams
Version: unspecifiedFlags: david_williams: pmc_approved+
arvera: pmc_approved? (raghunathan.srinivasan)
arvera: pmc_approved? (naci.dai)
deboer: pmc_approved+
arvera: pmc_approved? (neil.hauge)
arvera: pmc_approved? (kaloyan)
Target Milestone: 3.2.1   
Hardware: PC   
OS: Windows XP   
See Also: https://git.eclipse.org/r/108970
Whiteboard: PMC_approved
Attachments:
Description Flags
v1.0 none

Description Larina Cheung CLA 2010-05-18 16:01:52 EDT 
Build Identifier: 

In the Servers view, under the Timeout section, hit F1 on the Start and Stop controls does not display the help.  Please investigate the code.

OBSERVATIONS:
The ContextIds.java file contains these two entries:
public static final String EDITOR_TIMEOUT_START = ServerUIPlugin.PLUGIN_ID + "spge0026";
public static final String EDITOR_TIMEOUT_STOP = ServerUIPlugin.PLUGIN_ID + "spge0027";

Documentation is available:
<context id="spge0026">
<description>This is the length of time the workbench is going to wait for the server to start.
<b>Tip</b>:  If you have a fast processing machine, you can try specifying a shorter timeout interval.  If you have a slow processing machine, you can try specifying a longer timeout interval.
</description>
</context>

<context id="spge0027">
<description>This is the length of time the workbench is going to wait for the stop signal from the server.
<b>Tip</b>:  If you have a fast processing machine, you can try specifying a shorter timeout interval.  If you have a slow processing machine, you can try specifying a longer timeout interval.
</description>
</context>

Reproducible: Always
Comment 1 Angel Vera CLA 2010-05-19 09:51:10 EDT 
Created attachment 169111 [details]
v1.0

Upon investigation it looks like there is a . missing at beginning of the context ids. Eventhough this is a simple change, it is comming late in the cycle. I would like to postpone this fix until the next maintenance release
Comment 2 Angel Vera CLA 2010-07-09 21:34:00 EDT 
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. 
This is not a stop-ship, but something that we delayed from 3.2 into 3.2.1, because it came a little late in the cycle, we now want to put it in.

* Is there a work-around? If so, why do you believe the work-around is insufficient? 
No workaround.

* How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? 
I tested it by launching the workbench and ensuring the help displays.

* Give a brief technical overview. Who has reviewed this fix? 
adding a dot at the begging of the context id

* What is the risk associated with this fix? 
low, only compilation problems or that the contextid are incorrect and display help for a different item
Comment 3 Angel Vera CLA 2010-07-12 15:19:53 EDT 
Changes checked into 32M
Comment 4 Angel Vera CLA 2010-07-12 16:27:47 EDT 
Changes checked into HEAD
Comment 5 Angel Vera CLA 2010-07-12 16:27:58 EDT 
changes released to HEAD
Comment 6 Angel Vera CLA 2010-07-12 16:29:50 EDT 
changes released to 32M
Comment 7 Eclipse Genie CLA 2017-10-11 16:34:06 EDT 
New Gerrit change created: https://git.eclipse.org/r/108970