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

Bug 212039

Summary: Fix broken externalized strings for the Trace Project.
Product: z_Archived Reporter: Paul Slauenwhite <paulslau>
Component: TPTPAssignee: Ritwik Lodhiya <ritwikl>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P1 CC: jkubasta
Version: unspecifiedKeywords: plan
Target Milestone: ---Flags: jkubasta: review? (analexee)
jkubasta: review? (ewchan)
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Unused string Cleanup for trace none

Description Paul Slauenwhite CLA 2007-12-05 12:46:14 EST 
Fix broken externalized strings for the Trace Project.

Starting in Eclipse 3.2, the JDT provides a sub-menu on the Source context menu called "Find Broken Externalized Strings" for searching for broken externalized strings in a selected property file, package, project or set of projects:

http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm

Since translation is of property string or resource bundles is costly to the
project, each Project Lead should ensure unreferenced/unused translated
property strings and their resource bundle keys are removed.  

The Project Lead should ensure all resource bundles in their project's plug-ins are updated before 4.5 is released.

Note: Disregard the product/component for this defect since there is no Bugzilla component for general maintenance in a project.
Comment 1 Eugene Chan CLA 2007-12-05 13:37:14 EST 
Hi Joanna, would you please handle this for now?
Comment 2 Paul Slauenwhite CLA 2007-12-19 06:44:36 EST 
Can you include this in the 4.5 plan (P1 priority/plan keyword)?
Comment 3 Ritwik Lodhiya CLA 2008-02-01 11:22:25 EST 
Created attachment 88581 [details]
Unused string Cleanup for trace

This patch removes all un used strings from the trace project under HEAD.
Comment 4 jkubasta CLA 2008-03-14 07:20:20 EDT 
Alexander, Eugene, please review the attached patch.
Comment 5 jkubasta CLA 2008-03-14 10:00:19 EDT 
Sorry, didn't realize this was a duplicate bug

*** This bug has been marked as a duplicate of bug 216575 ***
Comment 6 Paul Slauenwhite CLA 2008-06-10 09:29:04 EDT 
Closing since same originator for both this defect and the dependent defect.