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

Bug 319934

Summary: [NLS] Confusing message when creating archive and variable references
Product: [WebTools] WTP Common Tools Reporter: Jason Peterson <jasonpet>
Component: wst.commonAssignee: Jason Peterson <jasonpet>
Status: RESOLVED FIXED QA Contact: Carl Anderson <ccc>
Severity: normal    
Priority: P3 CC: david_williams, jsholl
Version: 3.2Flags: david_williams: pmc_approved+
jasonpet: pmc_approved? (raghunathan.srinivasan)
jasonpet: pmc_approved? (naci.dai)
deboer: pmc_approved+
jasonpet: pmc_approved? (neil.hauge)
jasonpet: pmc_approved? (kaloyan)
ccc: review+
Target Milestone: 3.2.1   
Hardware: PC   
OS: Windows XP   
Whiteboard: PMC_approved
Attachments:
Description Flags
patch ccc: iplog+

Description Jason Peterson CLA 2010-07-14 19:52:20 EDT
Created attachment 174362 [details]
patch

The dialog for creating archive references (both external and workspace) as well as the dialog for creating variables contains the following additional message:

"This is not a suggested use-case, but is here for backwards compatibility"

This message is both confusing and unnecessary and should be removed.  The reason being that no suggested alternative is given for users wishing to duplicate this behavior.
Comment 1 Carl Anderson CLA 2010-07-14 23:32:55 EDT
I approve of this change.

This is a necessary usability improvement- the extraneous message is quite confusing.
Comment 2 Jason Peterson CLA 2010-07-15 08:26:24 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. 

The message scares users away from creating archive and variable references by mentioning that they are not recommended and only available for backwards compatibility.  However, no suggested alternative is given for users wishing to duplicate the functionality they provide.  

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

The workaround is to ignore the message and create the references anyways.  However, this gives users a sense of apprehension.

    * How has the fix been tested? Is there a test case attached to the
bugzilla record? Has a JUnit Test been added? 

Fix has been tested in the UI.

    * Give a brief technical overview. Who has reviewed this fix? 

The fix is remove the confusing and unnecessary message.

Carl has reviewed this fix.

    * What is the risk associated with this fix? 

None
Comment 3 Carl Anderson CLA 2010-07-15 11:48:38 EDT
Committed to HEAD for WTP 3.2.1 and WTP 3.3