Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312101 - Add F1 help for "Automatically publish after a build event"
Summary: Add F1 help for "Automatically publish after a build event"
Status: RESOLVED FIXED
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: wst.server (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 RC2   Edit
Assignee: Angel Vera CLA
QA Contact: Angel Vera CLA
URL:
Whiteboard: PMC_approved
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-07 13:08 EDT by Larina Cheung CLA
Modified: 2017-10-11 16:33 EDT (History)
1 user (show)

See Also:
arvera: pmc_approved? (david_williams)
raghunathan.srinivasan: pmc_approved+
arvera: pmc_approved? (naci.dai)
arvera: pmc_approved? (deboer)
arvera: pmc_approved? (neil.hauge)
arvera: pmc_approved? (kaloyan)

Attachments
PUblishing F1 screen capture (446.30 KB, image/bmp)
2010-05-07 15:05 EDT, Larina Cheung CLA 		no flags Details
v1.0 (2.39 KB, text/plain)
2010-05-17 11:45 EDT, Angel Vera CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Larina Cheung CLA 2010-05-07 13:08:25 EDT 
Build Identifier: 

Please assign the "Automatically publish after a build event" radio button a contextid: seop0014
referencing development plugin: org.eclipse.wst.server.ui

Reproducible: Always
Comment 1 Larina Cheung CLA 2010-05-07 15:04:25 EDT 
The seop0012 contextid seems to be duplicated for two different GUI elements:

1. Automatically publish when resources change
2. Publishing interval (in seconds)

Please correct the contextids as follows (attached is a screen capture):

(seop0016) Never publish automatically
(seop0012) Automatically publish when resources change
(seop0014) Automatically publish after a build event
(seop0018) Publishing interval (in seconds)
Comment 2 Larina Cheung CLA 2010-05-07 15:05:04 EDT 
Created attachment 167542 [details]
PUblishing F1 screen capture
Comment 3 Angel Vera CLA 2010-05-17 11:35:22 EDT 
I had a chat with Larina offline, and we reviewed the ids together. I have corrected the context ids as follow:

- The timer in the publishing section was indeed using a repeated id .seop0012, it is not pointing to .seop0018
- "Never publish automatically" is pointing to .seop0016
- "Automatically publish when resources change" is pointing to .seop0012
- "Automatically publish after a build event" was already pointing to .seop0014
- "Select publishing actions:" is pointing to .seop0020
Comment 4 Angel Vera CLA 2010-05-17 11:45:57 EDT 
Created attachment 168755 [details]
v1.0

* 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 it would correctly document the usage of our product

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

* How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? 
Launched WTP, set focus to the affected UI and then press F1

* Give a brief technical overview. Who has reviewed this fix? 
The fix is to crrectly set the context ids for the UI

* What is the risk associated with this fix? 
low, to minimal. Since the code changes affect only the help displayed at runtime
Comment 5 Angel Vera CLA 2010-05-17 11:51:39 EDT 
(In reply to comment #3)
correcting the typo not=now see the correct sentence below.

> - The timer in the publishing section was indeed using a repeated id .seop0012,
> it is [now] pointing to .seop0018
Comment 6 Angel Vera CLA 2010-05-18 12:33:39 EDT 
changes committed to HEAD
Comment 7 Angel Vera CLA 2010-05-18 13:29:39 EDT 
released to HEAD
Comment 8 Eclipse Genie CLA 2017-10-11 16:33:41 EDT 
New Gerrit change created: https://git.eclipse.org/r/108956